Public Repository

Last pushed: 2 months ago
Short Description
A SPA front-end on steroids.
Full Description

Quasar Framework

A SPA front-end on steroids.

Build responsive websites and hybrid mobile Apps (that look native!) using same code, with VueJs 2.

This container will give you access to the Quasar Framework in a development environment.

quasar-docker client-dev

Welcome to the Quasar client-dev container building setup. Follow the directions below, and you be running with a Docker container to develop a docker app in minutes.

docker-compose up

If you have cloned this repo, you should be in the /client-dev directory. Start a shell console in this directory and enter

$ docker-compose up -d

This will get the docker container clientdev_app_1 started and in detached mode.

When the container is building, it will take several minutes. Once the container is started, you should be back to the cursor in the shell.

To shut down the container, naturally the command is

$ docker-composer down

docker cp - copy files to the host

Once the container is running (or built), we'll need to get the initial files needed to work on Quasar from the container and onto the host. They have already been stored in the image and are on the new container. To get the files, carry out the following Docker "copy" command.

$ docker cp clientdev_app_1:/tmp/app .

You can now enter the /app directory.

This will be your starting point to develop with Quasar.

docker-compose exec

To get into the container to run the Quasar CLI commands necessary to work with Quasar, or to start the node server, run the following command.

$ docker-compose exec app sh

You should be in the /opt/app directory at this point. This directory is also a shared volume with the /app directory which you can develop in, so any changes to the files on the host are also reflected in the container.

npm install

Important: As a last step, before you can start developing with Quasar, you will need to run

/opt/app # npm install

so all the dependencies are installed too. If you wish to add any additional dependencies, please do so directly in the package.json file before you run the install.

At this point, you can use all the Quasar CLI commands.

For instance, if you'd like to start developing, you can enter

/opt/app # quasar dev mat

You should then be able to go to your browser and run http://docker.local:8080 and see the Quasar (move your mouse) welcome page. (or use the IP docker offers with

Or, if you'd like you can add a component with

/opt/app # quaser new component hello

You'll see the hello.vue component under the /src/components directory.

Running your own container from here

At this point, you should have a built image and a running container.

docker tag and push - save your work!

Once you make changes, you'll more than likely want to save it and upload the image to your repo on Docker Hub or any other container registry. To do this, first re-tag the image with the following command.

$ docker tag <image-id> <repository-name>/<image-name>:<[optional] tag>

This should have renamed your image.

Now you can "push" your image to the registry. If, for example, you are going to be using Docker Hub, you'll need to login first. To push the image to Docker Hub, use the following command.

$ docker push <repository-name>/<image-name>:<[optional] tag>

You'll probably also want to commit and push your code changes to Github or some other CVS.

Update the dockerfile and docker-compose.yml files

So, now you have your own image and will want to be a bit more efficient, when it comes to development. For that, you will notice the initial files also contain both a dockerfile and a docker-compose.yml file. You should edit these for your own development purposes.

In the dockerfile enter your own image name at the top on this line.

FROM quasarframework/client-dev:latest

and in the docker-compose.yml file, edit this line with your own image's name.

image: your-docker-org/your-app-name

docker-compose build - adding new dependencies

If you also now make changes to alter your packages.json file, you can then run the "build" command

$ docker-compose build

Following this step will allow you to save the new package(s) into the Docker layer holding the nmp modules for faster loading later, should you store your image on Docker Hub. Once the container build is finished, you can re-up your container and start working again.

If you have any questions, please use the Quasar forum or the If you have any issue or suggestions, we'd be happy if you could report them in Github.

That's it! Hope you enjoy the container and have fun with Quasar and Docker! :smile:

Docker Pull Command

Comments (0)