Help me test Tentacles Installation!
I want to make Tentacle a dream to install.
For the time being I would like to get a group of potential users to test the setup process.
The ideal tester should be a little techie, you don’t need to be a hard core nerd but you should understand what the errors mean.
And please send me feedback on the blog, or send a tweet, even an email.
Thanks!
Announcing the Inkdit API
Big news for the Inkdit team – today we’re officially opening up our API to the public! You can register and find documentation on our API’s site.
Our API allows developers at your organization to write applications that can create, share and sign contracts that will be securely stored with cryptographic tamper-resistance on Inkdit.
There are a lot of applications that involve agreements – license agreements, sign-offs, waivers, etc. Using Inkdit’s API your applications can capture those agreements in a tightly integrated way.
Shortly before the holidays we quietly released a Ruby library for interacting with Inkdit’s API (available as a gem named ‘inkdit’, with documentation here).
If you’re using we hope you’ll take a look at the library. If you’re not using Ruby, we hope you’ll look at it anyways – we’ve written it so that it can work as an example for other languages as well.
So what’s coming next? We’ve got big plans for our API; we have a sophisticated tiered user authentication system in the works, and we’d like to make that available for developers to build on top of.
The exciting thing about putting out an API is people are going to find uses for it that we’ve never thought of ourselves. We want to make it as easy as possible for people to use Inkdit to create new applications, so tell us what you need!
Is there a new application you’d like to see built on top of Inkdit?
Do you use an application that would integrate well with us?
Are there new capabilities you’d like us to expose to the API?
We’re looking into other languages to build libraries for. Is there a particular language that you would like code examples or a library for?
Via: Inkdit
DIY simple staging server.
While working on Tentacle I needed a simple solution for testing code on a remote web server.
In the past I would work locally and syncing with FTP to the server and then tested off of the remote server, I used SVN for my source control. Within the last year I have started working locally and using Git as my main source control.
This left a bit of a gap in my process where I could no longer test on a remote server without updating it manually by S/FTP or opening terminal and manually calling a git pull.
Open terminal and manually git pull it did break up the work flow a bit so using the Dingo framework I created a very simple Git helper and gave it its own URL something like git/pull.
I then used a Github Post-Receive URL Hook found under admin/service hooks that pointed to my staging server git pull URL, every time I do a push to Github, Github will then automatically fire the URL thus triggering the pull helper.
One little note is that if you check out a dev branch on a staging server and also have a live server you would add a second URL with the same code on that liver server. One push would update both sites.
Just make sure the live server is on the right branch.
If you don’t feel like using a hook then no problem at all. Just call the URL in the browser and you will see the Git pull message.