Difference between revisions of "Installation/EngineYard"
(Created page with "This wiki explains using "Git for Windows" to deploy your Diaspora test "fork" to EngineYard. It is my experience and has no affiliation with the Diaspora project. For a few ...")
Revision as of 18:59, 23 October 2012
This wiki explains using "Git for Windows" to deploy your Diaspora test "fork" to EngineYard. It is my experience and has no affiliation with the Diaspora project.
For a few reasons this environment i recommend only for testing.
- it is a service intended for developers - the disk storage is non-persistent - they do not offer or host SMTP services
1) GitHub: First setup a free account at GitHub. GitHub is a popular git repository. Git and GitHub can be confusing at first, don’t worry, keep going.
2) Git for Windows: Then download and install the latest version stable of GitHub for Windows. At the time of writing it is 1.0.7 http://windows.github.com/. Any Git for Windows will do, but GitHub for Windows is pre-configured for GitHub.
3) Cloud Server: Sign up for the EngineYard Cloud Free (Ruby) trial at http://www.engineyard.com/. Create your virtual server environment and application instance using default values. Boot the services with default values and use the one click install to install a self signed SSL certificate for testing. START by installing and testing the provided ToDo application and make sure that all works.
4) Diaspora: Go to https://github.com/diaspora/diaspora and make your own “fork” of the Diaspora code at GitHub. A fork is just your own copy of the code with version dependencies attached. Then use the [Clone] button to copy your forked repository to your local PC.
5) Deploy KEYS: When you create a git application at engineyard and specify the github address it will walk you through the process of creating and returning a deploy key from github. When things get confusing you can always nuke everything and start again… carry on… have fun…
6) Customize: Before you deploy there are just a few files that need to be created to configure your default Diaspora code to your engineyard cloud environment. They are “diaspora.yml” and “database.yml” which are NOT found in the “config” directory as part of the git package. To create them, make SURE that Git for Windows is running, use it to open an explore to your repository. Open the provided diaspora.yml.example file, make the needed changes to the URL and Pod Name etc, then save the file without the “.example” extension. Do the same with database.yml. No changes need to be made to the default file database.yml in this case. Then “commit” and “sync” as needed in Git for windows. Make sure it shows up as ‘in sync’ before you continue.
For image re-sizing to work properly on EngineYard you must set single_process_mode: true in your config/diaspora.yml. Otherwise thumb nail images will retain the original data size, which is not good. EngineYard does not seem to run background task in a separate process. You must run the re-size task within the request cycle, but performance by the cloud services seems good enough for testing without.
7) Deploy: At engineyard you should now be able to use the [DEPLOY] button and run Diaspora in “development mode” on your booted application instance. Check the box that says to Rake and Migrate the DB. This will create an empty database for the app.
8) Test: Go to your URL or IP address and you should see a working Diaspora application. You may have some browser warnings about SSL and some problems with connecting to other pods due to the self signed certificate. But you should be able to find and display known members of remote pods by handle firstname.lastname@example.org from the search box. If that works then you can install a free Class 1 SSL cert from various providers (such as startssl.com or sslshopper.com just for example) for a more complete testing of Diaspora’s features.
You probably ran into some problem along the way… that’s normal… nuke everything… do it again… and again… and again… cause it will work in the end. It’s a great free way to get familiar with the ropes. When your ready you can setup for deployment of a small pod on your own linux box, or even the deployment of a tier pod on a production host. Good luck!
Keep up to date with code changes on GitHub by following the project members. If you find errors or missing information or useful tips or links please add them here! Explore code, pull updates, make changes and redeploy your fork! If you find bugs or have suggestions please contribute!