# Capistrano e le release **URL:** \ **Category:** IT\ **Created:** [February 28, 2009, 12:13am UTC](https://www.ruby-forum.com/t/capistrano-e-le-release/161625 "2009-02-28T00:13:18Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![msan](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/3ab097/32.png) [@msan](https://www.ruby-forum.com/u/msan)\ **Post date:** [February 28, 2009, 12:13am UTC](https://www.ruby-forum.com/t/capistrano-e-le-release/161625/1 "2009-02-28T00:13:18Z")
Oggi ho installato e fatto il primo deploy con capistrano. Devo ancora vedere come utilizzarlo con passenger poiche’ la maggior parte dei tutorials in rete fanno riferimento a mongrel o webrick come layer. Mi pare di capire che ogni volta che faccio delle modifiche all’applicazione devo rifare il deploy per riflettere tali modifiche anche nell’ambiente di produzione. Ad ogni deploy mi viene creata una directory release l’ultima delle quali viene linkata a current. Se le vecchie releases non dovessero servirmi piu’ esiste qualche comando di capistrano che mi permette di eliminarle oppure devo intervenire a mano sul server? ---
**Author:** ![msan](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/3ab097/32.png) [@msan](https://www.ruby-forum.com/u/msan)\ **Post date:** [February 28, 2009, 4:55pm UTC](https://www.ruby-forum.com/t/capistrano-e-le-release/161625/2 "2009-02-28T16:55:01Z")
Ciao! “cap deploy:cleanup” dovrebbe fare al caso tuo. s/v 2009/2/28 Mauro [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid): > comando di capistrano che mi permette di eliminarle oppure devo > intervenire a mano sul server? > > * * * > > Ml mailing list > removed\_email\_address@domain.invalid > [http://lists.ruby-it.org/mailman/listinfo/ml](http://lists.ruby-it.org/mailman/listinfo/ml) – Considera l’ambiente prima di stampare questa email. Dai, che l’equazione è semplice: meno A4, più alberi. . . . Silvano S. . . . email: removed\_email\_address@domain.invalid site: [http://www.sistrall.it](http://www.sistrall.it) ---
**Author:** ![msan](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/3ab097/32.png) [@msan](https://www.ruby-forum.com/u/msan)\ **Post date:** [February 28, 2009, 5:37pm UTC](https://www.ruby-forum.com/t/capistrano-e-le-release/161625/3 "2009-02-28T17:37:19Z")
confermo 😃 On Sat, Feb 28, 2009 at 3:54 PM, Silvano S. \< ---
**Author:** ![msan](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/3ab097/32.png) [@msan](https://www.ruby-forum.com/u/msan)\ **Post date:** [February 28, 2009, 10:46pm UTC](https://www.ruby-forum.com/t/capistrano-e-le-release/161625/4 "2009-02-28T22:46:52Z")
2009/2/28 Sandro P. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid): > confermo 😃 > > On Sat, Feb 28, 2009 at 3:54 PM, Silvano S. \< > removed\_email\_address@domain.invalid\> wrote: > > > Ciao! > > > > “cap deploy:cleanup” dovrebbe fare al caso tuo. Per capire se ho fatto bene: dopo aver configurato il file deploy.rb ho lanciato cap deploy:setup e poi cap deploy:update, e’ sufficente questo? Considerando che uso passenger come layer e non mongrel. ---
**Author:** ![msan](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/3ab097/32.png) [@msan](https://www.ruby-forum.com/u/msan)\ **Post date:** [March 1, 2009, 11:56am UTC](https://www.ruby-forum.com/t/capistrano-e-le-release/161625/5 "2009-03-01T11:56:28Z")
2009/2/28 Sandro P. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid): > confermo 😃 Mah l’ho provato cap deploy:cleanup ma mica mi ha eliminato la vecchia release. ---
**Author:** ![msan](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/3ab097/32.png) [@msan](https://www.ruby-forum.com/u/msan)\ **Post date:** [March 1, 2009, 6:35pm UTC](https://www.ruby-forum.com/t/capistrano-e-le-release/161625/6 "2009-03-01T18:35:55Z")
2009/3/1 Mauro [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid): > 2009/2/28 Sandro P. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid): > > > confermo 😃 > > Mah l’ho provato cap deploy:cleanup ma mica mi ha eliminato la vecchia release. di default tiene lo storico delle ultime 5 release deployate. m. ---
**Author:** ![msan](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/3ab097/32.png) [@msan](https://www.ruby-forum.com/u/msan)\ **Post date:** [March 1, 2009, 10:48pm UTC](https://www.ruby-forum.com/t/capistrano-e-le-release/161625/7 "2009-03-01T22:48:43Z")
2009/3/1 Michele F. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid): > 2009/3/1 Mauro [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid): > > > 2009/2/28 Sandro P. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid): > > > > > confermo 😃 > > > > Mah l’ho provato cap deploy:cleanup ma mica mi ha eliminato la vecchia release. > > di default tiene lo storico delle ultime 5 release deployate. Ah ecco, ok 🙂 ---
**Author:** ![msan](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/3ab097/32.png) [@msan](https://www.ruby-forum.com/u/msan)\ **Post date:** [March 9, 2009, 4:45pm UTC](https://www.ruby-forum.com/t/capistrano-e-le-release/161625/8 "2009-03-09T16:45:14Z")
Msan M. wrote: > 2009/3/1 Mauro [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid): > > > > > Per conferma: cap deploy:setup per il primo deploy, successivamente > cap deploy:update mentre per i successivi deploy sempre cap > deploy:update. > Non c’e’ da far altro no? Ciao Msan, puoi dare uno sguardo a questo post: > **[Acinapura.com is for sale | HugeDomains](https://www.hugedomains.com/domain_profile.cfm?d=acinapura.com)** > > Choose a memorable domain name. Professional, friendly customer support. Start using your domain right away. Dovrebbe aiutarti a capire meglio come funziona Capistrano A presto, Vincenzo ---
**Author:** ![msan](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/3ab097/32.png) [@msan](https://www.ruby-forum.com/u/msan)\ **Post date:** [March 1, 2009, 10:49pm UTC](https://www.ruby-forum.com/t/capistrano-e-le-release/161625/9 "2009-03-01T22:49:53Z")
2009/3/1 Mauro [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid): > Per conferma: cap deploy:setup per il primo deploy, successivamente cap deploy:update mentre per i successivi deploy sempre cap deploy:update. Non c’e’ da far altro no?