Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Support project-based config dir #115

Open
moltar opened this issue Jun 23, 2019 · 2 comments
Open

Support project-based config dir #115

moltar opened this issue Jun 23, 2019 · 2 comments
Labels
enhancement New feature or request. solutioning The issue is not being implemented but only analyzed and planned. t-platform Issues with this label are in the ownership of the platform team.

Comments

@moltar
Copy link

moltar commented Jun 23, 2019

Use case: I am juggling multiple client accounts and I need to be able to push to different accounts.

Currently only one account is supported via GLOBAL_CONFIGS_FOLDER.

https://github.com/apifytech/apify-cli/blob/cfbd6566f7c41eb5ce0b6e3e74aa1e96970b1d13/src/lib/consts.js#L100

Ideally it should allow for project-based config dir (e.g. .../project/.apify/*), and/or allow having multiple accounts under the homedir (e.g. $HOME/.apify/acc1).

Inspiration can be taken from aws-cli or kubectl.
@drobnikj drobnikj added the enhancement New feature or request. label Jul 26, 2019
@uiii
Copy link

uiii commented Jul 26, 2022

any progress on this?

@mnmkng
Copy link
Member

mnmkng commented Jul 26, 2022 •
edited
Loading

No, sorry. But it's not dead, we're just completely reworking the way this and many other things will be handled. For reference see the Actor specs

@mtrunkat mtrunkat added t-platform Issues with this label are in the ownership of the platform team. and removed feature request labels Aug 1, 2022
@mtrunkat mtrunkat mentioned this issue Aug 1, 2022
Open
@mtrunkat mtrunkat added solutioning The issue is not being implemented but only analyzed and planned. next sprint Check this out when planning next sprint. labels Aug 1, 2022
@fnesveda fnesveda removed the next sprint Check this out when planning next sprint. label Aug 25, 2022
@B4nan B4nan mentioned this issue Mar 11, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request. solutioning The issue is not being implemented but only analyzed and planned. t-platform Issues with this label are in the ownership of the platform team.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@uiii @moltar @mtrunkat @fnesveda @drobnikj @mnmkng