[p2pu-dev] Problems with Vagrant
Chris Ewald
chris at p2pu.org
Fri Jul 27 11:54:27 UTC 2012
In the project directory, typing vagrant ssh will give you a terminal ash
connection. From there it's the same as any other remote machine. Type
python lernanta/manage.py runs sever or whatever. To restart do vagrant
halt from the host and then vagrant up.
The correct user and virtualenv is already setup. When you sah it will say
lernanta because it switched to that virtualenv already.
All this is on the readme on github I believe
On Friday, July 27, 2012, Dirk Uys wrote:
> Hi Stian, Chris
>
> I haven't checked that out myself, have you been able to resolve to
> problem?
>
> I would also like to know a few things when using vagrant:
>
> - How do I run a normal manage command?
> - How can I restart the development server? It sometimes crashes when I
> make syntax errors while editing files.
> - How do I get a django shell?
>
> Can we maybe create a shortcut that will su to the correct user and
> activate the virtualenv?
>
> Maybe we can compile a Vagrant cheatsheet/cookbook -
> http://pad.p2pu.org/p/vagrant
>
> Cheers
> d
>
> On Fri, Jul 13, 2012 at 4:55 PM, Chris Ewald <chris at p2pu.org> wrote:
>
> Not sure about that one. We will have ask to ask dirk.
>
> I don't have that file in my repo. I guess you copied it in. It looks like
> it should be placed in the top lernanta folder. Same one as the settings
> files and and the manage.py.
>
> That's my best guess for now.
>
>
> On Fri, Jul 13, 2012 at 4:46 PM, Stian Håklev <shaklev at gmail.com> wrote:
>
> Great, ssh works :) compilemessages still doesn't though
>
> (lernanta)p2pu at precise32:/opt/lernanta/lernanta/locale/zh_CN/LC_MESSAGES$
> django-admin.py compilemessages
> Error: This script should be run from the Django SVN tree or your project
> or app tree, or with the settings module specified.
>
> Stian
>
> On Fri, Jul 13, 2012 at 10:44 AM, Chris Ewald <chris at p2pu.org> wrote:
>
> Updating the readme...
>
>
> On Fri, Jul 13, 2012 at 4:44 PM, Chris Ewald <chris at p2pu.org> wrote:
>
> cd into the top project directory.
>
>
> On Fri, Jul 13, 2012 at 4:41 PM, Stian Håklev <shaklev at gmail.com> wrote:
>
> Thanks a lot for your support.
>
> More fun error messages:
>
> stian at Monkey ~/s/l/l/l/l/z/LC_MESSAGES> vagrant ssh
> /Users/Stian/src/lernanta-dev-env/Vagrantfile:85:in `read': No such file
> or directory - ./node.json (Errno::ENOENT)
> from /Users/Stian/src/lernanta-dev-env/Vagrantfile:85:in `block (2
> levels) in <top (required)>'
> from
> /usr/local/lib/ruby/gems/1.9.1/gems/vagrant-1.0.3/lib/vagrant/config/vm/provisioner.rb:32:in
> `call'
> from
> /usr/local/lib/ruby/gems/1.9.1/gems/vagrant-1.0.3/lib/vagrant/config/vm/provisioner.rb:32:in
> `configure'
> from
> /usr/local/lib/ruby/gems/1.9.1/gems/vagrant-1.0.3/lib/vagrant/config/vm/provisioner.rb:21:in
> `initialize'
> from
> /usr/local/lib/ruby/gems/1.9.1/gems/vagrant-1.0.3/lib/vagrant/config/vm.rb:71:in
> `new'
> from
> /usr/local/lib/ruby/gems/1.9.1/gems/vagrant-1.0.3/lib/vagrant/config/vm.rb:71:in
> `provision'
> from /Users/Stian/src/lernanta-dev-env/Vagrantfile:78:in `block in <top
> (required)>'
> from
> /usr/local/lib/ruby/gems/1.9.1/gems/vagrant-1.0.3/lib/vagrant/config/loader.rb:83:in
> `call'
> from
> /usr/local/lib/ruby/gems/1.9.1/gems/vagrant-1.0.3/lib/vagrant/config/loader.rb:83:in
> `block (2 levels) in load'
> from
> /usr/local/lib/ruby/gems/1.9.1/gems/vagrant-1.0.3/lib/vagrant/config/loader.rb:79:in
> `each'
> from
> /usr/local/lib/ruby/gems/1.9.1/gems/vagrant-1.0.3/lib/vagrant/config/loader.rb:79:in
> `block in load'
> from
> /usr/local/lib/ruby/gems/1.9.1/gems/vagrant-1.0.3/lib/vagrant/config/loader.rb:76:in
> `each'
> from
> /usr/local/lib/ruby/gems/1.9.1/gems/vagrant-1.0.3/lib/vagrant/config/loader.rb:76:in
> `load'
> from
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.p2pu.org/pipermail/p2pu-dev/attachments/20120727/8eeb2202/attachment.html>
More information about the p2pu-dev
mailing list