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 for microservices #139

Open
1 of 4 tasks
pavjacko opened this issue Jul 10, 2019 · 2 comments
Open
1 of 4 tasks

Support for microservices #139

pavjacko opened this issue Jul 10, 2019 · 2 comments
Assignees
@pavjacko @lukutism
Labels
enhancement New feature or request full sanity required This change has potential impact on all existing projects pinned

Comments

@pavjacko
Copy link
Member

pavjacko commented Jul 10, 2019 •
edited by lukutism
Loading

Add ability to create backend microservice in ReNative project and debug/deploy it as part of dev workflow

Connectors to support STAGE 1:

  • Now
  • AWS S3
  • AWS Lambda
  • FTP
@pavjacko pavjacko added the enhancement New feature or request label Jul 10, 2019
@pavjacko pavjacko self-assigned this Jul 10, 2019
@lukutism lukutism self-assigned this Jul 31, 2019
@maximilize
Copy link
Collaborator

maximilize commented Aug 6, 2019 •
edited
Loading

The fact that the now package always needs downloads a 60 MB binary file on a npm install is quite annoying, especially on slow internet connections (hotels etc.). Also many users will never use this service, so it's mainly just bloatware?

Is it really a good idea to integrate the deployment code to 3rd party services into the rnv binary?
If ever, I suggest to move deployment code to another package, like rnv-deploy, or to make this dependencies optional if this is possible somehow.

@stale
Copy link

stale bot commented Nov 1, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix This will not be worked on label Nov 1, 2019
@mihaiblaga89 mihaiblaga89 added pinned and removed wontfix This will not be worked on labels Nov 1, 2019
@pavjacko pavjacko added the full sanity required This change has potential impact on all existing projects label May 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pavjacko pavjacko

@lukutism lukutism

Labels
enhancement New feature or request full sanity required This change has potential impact on all existing projects pinned
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@maximilize @pavjacko @mihaiblaga89 @lukutism