Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Talk proposal: Automated Project Setup Best Practices #87

Open
wants to merge 7 commits into
base: master
Choose a base branch
from

Conversation

matisojka
Copy link

As Ruby on Rails projects become larger and more complex, more local and remote services are needed by the applications. New teammates, unequal distribution of knowledge, keeping the setup documentation up-to-date, running the test infrastructure and many more problems can easily get out of control.

Find out, how to successfully manage the chaos using real world solutions. We want to share our project experiences using an automated setup, heaps of Ruby tools, complex deployment scripts and the use of cloud services to save time, money and lots of headache.

Watch more in the video:

@mediafinger
Copy link

Guess we have all been at that point - learning about a good and proven solution wouldn't hurt!

@awendt
Copy link

awendt commented Mar 27, 2012

+1

1 similar comment
@benzimmer
Copy link

+1

@thomasritz
Copy link

+1 Developing an automated setup template for large environments that works for most if not all of your projects is really the hard part nowadays. Especially if you don't want to remember what's special in each of your server setups. I wish it would be a no-brainer these days...

@apepper
Copy link

apepper commented Apr 2, 2012

+1

1 similar comment
@ghost
Copy link

ghost commented Apr 3, 2012

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants