Frontastic CLI for Windows
Frontastic CLI is the central entry point for frontend development with Frontastic. It's possible to run webpack, which prepares all frontend code, directly on your machine and everything else in the Cloud.
Unfortunately, support for Frontastic CLI on Windows is still limited but we're working on improving this.
For now, if you're using Windows, you'll need to use a Frontastic Machine for frontend development.
You'll have problems if you run Frontastic CLI in the same checkout as a container/VM. You need to do a clean Git checkout of your project. Also, Frontastic CLI requires that there's no container/VM with Frontastic running on your machine when using it.
To get Frontastic CLI running on your Windows system, you'll need to download the package from the Frontastic CLI release page.
Then head to the Frontastic Editor and bring up a new machine. For full steps on how to do this, see the Frontastic Machine article.
frontastic initin the root directory of your code repository checkout
You can repeat this step later when you want to change the configuration.
ssh-keygen -t ed225519 -a 100, make sure to use the default filename (for example,
$HOME/.ssh/id_ed25519). Do not set a password
ssh firstname.lastname@example.org without asking for anything
checkssh = falsein
You can now access your development environment under:
When you're done for the day, you can stop the development service by hitting
Yarn has errors on installation
Please make sure you've done a fresh checkout after using a container/VM. Or you can remove all
node_modules folders (even those in
paas/...) and try again. You can clean up your entire code base to the state of a fresh clone using
git clean -f -d -x.
Frontastic CLI claims ports are in use
You might have a Frontastic container/VM running in another directory. Make sure this is shut down properly using
vagrant halt in the directory in question. Another reason might be that you have a webserver running locally on port
80 please shut this down before starting the Frontastic CLI.
In rare cases, there might also be a dangling process of a utility used by Frontastic CLI. To check this, see if there are processes running named
traefik. If so, terminate those and try again. If that does still not help, restarting your computer to release the ports from zombie processes might help.
‹ Back to article list