GithubHelp home page GithubHelp logo

Comments (5)

pascalbreuninger avatar pascalbreuninger commented on July 20, 2024 1

Hi @QAston, sounds like a good addition. We've discussed adding an --additional-files flag to devpod up which would

  1. Stream these files to the remote machine
  2. Mount them into the devcontainer
  3. Expose them to lifecycle commands

This would also solve your problem, right?

from devpod.

QAston avatar QAston commented on July 20, 2024

In case we want to be able to run some logic as well to select/prepare files, so I'd personally prefer a custom hook in the config file, similar to the existing hooks but guaranteed to be run on the devpod cli machine. Just having a flag that has to be manually added doesn't provide much over our current approach of wrapping the cli and scp in the wrapper script.

from devpod.

pascalbreuninger avatar pascalbreuninger commented on July 20, 2024

fair enough. Be aware that if you rely on the customization to spin up your environment correctly you'd loose the ability to create workspace with other supporting tools and you'd expect everybody to have these files on their machines outside of your git repository. This basically creates a loop where you'd now have to standardize the environment again

from devpod.

QAston avatar QAston commented on July 20, 2024

In our case this is for optimistically forwarding configuration like git user.name user.email and similar. People have ability to customize and add more options by making a branch of the repository with the devpod config. If the current host-init (initializeCommand) step is not a threat to standardizing the enrionment, a devpod specific step shouldn't be a bigger problem.

Essentially, devpods already do this for docker and ssh-agent and git crednetial helper, it'd be nice to have something that covers custom systems.

from devpod.

euven avatar euven commented on July 20, 2024

Hi @QAston, sounds like a good addition. We've discussed adding an --additional-files flag to devpod up which would

1. Stream these files to the remote machine

2. Mount them into the devcontainer

3. Expose them to lifecycle commands

This would also solve your problem, right?

This would solve our problem! :)

from devpod.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.