You can use on :start.
on :start, local:populate_roles
-- Simone
On Mon, Jun 14, 2010 at 1:02 PM, Robin Bowes robin-li...@robinbowes.comwrote:
Hi,
I'd like to run a local task before anything else runs (to populate my
roles). Is there a callback I can use to do that?
eg. I'm doing
:
On 14/06/10 12:09, Simone Carletti wrote:
You can use on :start.
on :start, local:populate_roles
Simone,
Thanks, that looks like what I need.
R.
--
* You received this message because you are subscribed to the Google
Groups Capistrano group.
* To post to this group, send email
dynamically?
For example, most of my node data is stuffed in a central database by
puppet, and it's real easy to pull out hostnames with ActiveRecord,
question is how do I fill in roles with this?
--
Joe McDonagh
Operations Engineer
www.colonfail.com
--
Simone Carletti
Site Blog
Capistrano should be smart enough to echo a kind of
deprecation warning if the Rails version belongs to the 2.2 branch and is
lower than 2.3. This would prepare users in case of the project is going to
be upgraded.
What do you think?
--
Simone Carletti
Site Blog: http://www.simonecarletti.com
successful commands:
--
Simone Carletti
Site Blog: http://www.simonecarletti.com
Email: wep...@weppos.net
LinkedIn: http://linkedin.com/in/weppos
Nick: weppos | Skype: weppos
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
On Tue, Aug 4, 2009 at 12:59 PM, Lee Hambley lee.hamb...@gmail.com wrote:
SImone, that's fantastic news, if you get a moment could you throw tickets
in lighthouse for the other two, the problems they solve and maybe a tiny
usage case
Done.
--
Simone Carletti
Site Blog: http
://is.gd/1s5W1
2009/5/22 Simone Carletti wep...@gmail.com
Hi Lee,
On Fri, May 22, 2009 at 2:30 PM, Lee Hambley lee.hamb...@gmail.comwrote:
but I will pull it from github later
Great! Let me know if you run into any problem.
ps, anyone interested can follow @capistranorb on twitter
) the files because including production.rb and development.rb files
at the same time might cause some incompatibilities due to
constants/configuration redefinition) I ended up with that patch.
I confess I didn't completely discard the idea to work on that feature too.
--
Simone Carletti
Site Blog
when it runs
rake db:migrate.
--
Simone Carletti
Site Blog: http://www.simonecarletti.com
Email: wep...@weppos.net
LinkedIn: http://linkedin.com/in/weppos
Nick: weppos | Skype: weppos
--~--~-~--~~~---~--~~
You received this message because you are subscribed
the gem
- adapt those lines
--
Simone Carletti
Site Blog: http://www.simonecarletti.com
Email: wep...@weppos.net
LinkedIn: http://linkedin.com/in/weppos
Nick: weppos | Skype: weppos
--~--~-~--~~~---~--~~
To unsubscribe from this group, send email to
capistrano
Hi Lee,
On Fri, May 22, 2009 at 2:30 PM, Lee Hambley lee.hamb...@gmail.com wrote:
but I will pull it from github later
Great! Let me know if you run into any problem.
ps, anyone interested can follow @capistranorb on twitter if they want
regular updates.
Done.
--
Simone Carletti
Site
I'm not sure how to use this to solve problems. The key needs to go
somewhere, and so we're back to square one, on where to store the key.
What do you do? Is there a best practice? What do the large
enterprise / J2EE shops do?
--
Simone Carletti
Site Blog: http
The first solution that comes to my mind is to use the Capistrano Multistage
extension.
http://github.com/jamis/capistrano-ext/tree/master
I'm using this extension to configure multiple environments (and
consequently capistrano deployments) on the same server.
You can create two stages, one for
In this case you might want to create a migration Rails environment pointing
to the production database but with the migration user. Then, ask Capistrano
to execute db:migrate with migration environment.
With this configuration you don't need odd workarounds to switch users in
the same production
I usually grant all privileges to the database user except the ability to
GRANT or remove other permissions.
User access is restricted by IP to prevent unauthorized access from an
external client.
Capistrano itself doesn't provide any special task for changing privileges
but you can extend the
You should use Rails Migrations.
http://api.rubyonrails.org/classes/ActiveRecord/Migration.html
Then when you deploy your Rails app you simply need to ask capistrano to run
pending migrations after the code checkout.
There are a couple of tasks to do so.
cap deploy:migrate runs pending
mongrel_cluster-1.0.5
mysql-2.7
rails-1.2.6
rake-0.8.2
rmagick-2.6.0
sources-0.0.1
--
Simone Carletti
Site Blog: www.simonecarletti.com
Email: wep...@weppos.net
LinkedIn: http://linkedin.com/in/weppos
Nick: weppos | Skype: weppos
Thanks for your feedback Karel!
I agree that Capistrano needs more documentation and I'm happy to hear
someone else is available to contribute.
I must confess I didn't notice your message before, I'm going to post a
reply at http://groups.google.com/group/capistrano/msg/654e5e84d45f9098
Talking
My 2 cents about this topic.
I agree that Capistrano needs more documentation.
From one side I agree with Jamis that rdoc is not useful at all for
people who wants to *use* Capistrano, but it might be helpful for
those who wants to *extend* or play with it at development level.
When I first
I've been prompted to finish hashing out a load of blog articles that have
been sitting round my site as drafts since forever... and get them made into
real posts - I think I posted two yesterday, and will continue to post
anything I think is useful.
The same here! :D
Maybe someone should
I'm actually working on a couple of Capistrano new features.
I contacted Jamis on January and he gave me some good ideas about how
implement them.
Unfortunately, it seems I finished them too late.
All the features are available in my Capistrano fork on github.
21 matches
Mail list logo
