No More Posting New Topics!

If you have a question or an issue, please start a thread in our Github Discussions Forum.
This forum is closed for new threads/ topics.

Navigation

    Quasar Framework

    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search

    Docker dev container available

    Show & Tell
    2
    3
    1237
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • s.molinari
      s.molinari last edited by

      Hi,

      I’m looking for testers and feedback for my alpha version docker setup.

      https://github.com/smolinari/quasar-docker

      This is just a starting container environment for development purposes only. Distribution containers will be created later, along with some backend example containers for development too.

      The idea of this dev container is to allow the developer to “shell into” the container to run the CLI and develop Quasar through the container, but from within the directory they are currently working in. It allows for the CLI init process and all build processes. Basically, the whole CLI should work (that is what needs testing.)

      Any suggestions for improvement and feedback in general would be greatly appreciated. You can create issues directly in the repo.

      Thanks!

      Scott

      1 Reply Last reply Reply Quote 1
      • U
        UnderDog last edited by

        Hi Scott,
        Container looks good (haven’t installed it yet) can you think of also installing yarn in that same container?
        I need a laravel 5.7 backend as API as example, not ‘localhost’
        Maybe separate repo?

        1 Reply Last reply Reply Quote 0
        • s.molinari
          s.molinari last edited by

          @UnderDog - I’m using a generic node alpine container and installing yarn would just lengthen the process, unfortunately.

          You can create your own base container (there might even be one already done with yarn) as you’d like it and just update the Dockerfile container import (FROM) accordingly.

          Scott

          1 Reply Last reply Reply Quote 0
          • First post
            Last post