-
-
Notifications
You must be signed in to change notification settings - Fork 80
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
Toolchain: Issues following a dev environment setup #221
Comments
Ah yes, I have been saying it's broken, but it's not actually broken, just not documented. Using the When the VM is running, you should be able to use http://ludumdare.org to access your webserver (it's mapped to 192.168.48.48). It will only work on your local machine though. To test locally on remote or mobile devices, you need a router that lets you change its hosts file. Accessing the site via IP addresses and ports probably wont be supported anymore, due to the way cookies across domains are handled. There's a few tools that needed newer versions from 3rd party repos, I just can't remember which ones. SVGO might have been completely broken (that seems to ring a bell). Either that, or it needed an actual current version of NPM and Node (not what ships in the Ubuntu repos). That said, I might just be remembering the hell that was trying to get Grub to support multiple build targets, hence why it's now a Makefile. On my setup, I have them installed outside the VM, and do my builds there. There was a reason for that, but I can't remember what (Grub again maybe). I run Ubuntu 16.04. |
Some notes on installing the toolchain from outside the VM. These steps are untested inside the VM (i.e.
EDIT: Actually not finally. Don't forget to upgrade MySQL to MariaDB, or any features that rely on IP addresses wont work (Love). See #301 |
Alright, the above added instructions should work for anyone attempting to install the toolchain. My bad, but it looks like I forgot to push an update to the DairyBox repo way back in August. It was in my repo, but not mainline Ludum Dare's. If you decide to upgrade your NodeJS via NodeSource, you'll need to use Node dependencies can be upgrade as follows.
|
Getting PHP7 running in the VM isn't necessarily straightforward. scotch-io/scotch-box#157 (comment) That said, I did try following my instructions above but with |
A "stock" install of
|
Alright! This should finally be fixed.
Windows setup instructions still need to be added, but that's a different issue. |
In the README, the URL for PHPMyAdmin is missing the 'dev' part, it's currently http://192.168.48.48/phpmyadmin/, and should be http://192.168.48.48/dev/phpmyadmin/ |
Ah shoot. I think I did merge in a fix that corrected this, but I might have messed it up. |
Okay this is fixed. I see why it wasn't fixed. |
I still get a 404 not found at http://192.168.48.48/phpmyadmin/, after updating and running |
It was moved to /dev/ |
You might have to run |
Ok, my bad. I was looking at the documentation in my own fork and wondering why the url hadn't been updated 😅 I can access it at http://192.168.48.48/dev/phpmyadmin/ |
Proudly, I'm going to close this. There are new issues of course (toolchain should generate some sample content), but that is a separate issue. |
Hi,
I've seen the big "BROKEN" warning in the readme but you may be interested in this list of little tweaks I had to do to get things to run (after setting things up as documented):
Outside the VM
cd www/src/tools && chmod 777 *
vagrant halt && vagrant up
Inside the VM
I didn't look into it too much but the
all.min.svg
files didn't appear in my-
folder, though thesvgo
commands seemed to run without errors. So unfortunately I couldn't enjoy the new LD logo in its full SVG glory :PThe text was updated successfully, but these errors were encountered: