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.

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

Allow publishing existing place file with 'rojo upload' #94

Closed
LPGhatguy opened this issue Jan 10, 2019 · 2 comments
Closed

Allow publishing existing place file with 'rojo upload' #94

LPGhatguy opened this issue Jan 10, 2019 · 2 comments
Labels
impact: high Major blocker for Rojo users, or stops people from adopting Rojo. scope: cli Relevant to the Rojo CLI type: enhancement Feature or improvement that should potentially happen

Comments

@LPGhatguy
Copy link
Contributor

Right now, rojo upload generates the place file that it uploads for you. Since not all instances are supported by Rojo right now, this severely limits the kinds of places that can be automatically deployed.

It should accept an optional parameter, maybe --place, that is a path to an existing place file to upload instead of generating a new one.

@LPGhatguy LPGhatguy added type: enhancement Feature or improvement that should potentially happen impact: high Major blocker for Rojo users, or stops people from adopting Rojo. labels Jan 10, 2019
@Kampfkarren
Copy link
Member

I'm wondering if its within scope for Rojo to become the new Ropp in this regard.

@LPGhatguy LPGhatguy added the scope: cli Relevant to the Rojo CLI label Feb 8, 2019
@LPGhatguy
Copy link
Contributor Author

I believe this would be better off implemented in a tool that is not Rojo. I've been considering this functionality as part of rojo-rbx/remodel#16 instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
impact: high Major blocker for Rojo users, or stops people from adopting Rojo. scope: cli Relevant to the Rojo CLI type: enhancement Feature or improvement that should potentially happen
Projects
None yet
Development

No branches or pull requests

2 participants