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

publish sites privately to aws S3 with http basic auth #123

Closed
edavidaja opened this issue Sep 12, 2018 · 5 comments
Closed

publish sites privately to aws S3 with http basic auth #123

edavidaja opened this issue Sep 12, 2018 · 5 comments

Comments

@edavidaja
Copy link
Contributor

In thinking about ways to publish workflowr sites privately, I happened across the following:

https://hackernoon.com/serverless-password-protecting-a-static-website-in-an-aws-s3-bucket-bfaaa01b8666

which has been mostly automated by a repository referenced in the article, and linked to here.

Introducing it to the package would add some aws dependencies, but if nothing else it might be worth a mention in the docs as a way to accomplish that goal if you really want a private workflowr website.

@jdblischak
Copy link
Member

https://hackernoon.com/serverless-password-protecting-a-static-website-in-an-aws-s3-bucket-bfaaa01b8666

@edavidaja Thanks for the tip! Have you tried following the instructions to set up a password-protected site yourself?

Introducing it to the package would add some aws dependencies, but if nothing else it might be worth a mention in the docs as a way to accomplish that goal if you really want a private workflowr website.

Yes, I see 3 possible options. Ordered in increasing complexity:

  1. Add this URL to the FAQ on private web hosting
  2. Include longer-form documentation tailored to workflowr users on how to implement this solution
  3. Write a new function to deploy the site to Amazon S3 using the aws.s3 package

Would you be interested in helping implement any of these solutions?

@edavidaja
Copy link
Contributor Author

I'll send a PR updating the FAQ in a few hours. Once I've had an opportunity to actually get a demo site up and running, I can also add a vignette about private deployments. I suspect 3 is slightly outside my level of package development skill, so no commitments there, but if I make it happen, I'm happy to submit that later as well.

@jdblischak
Copy link
Member

I'll send a PR updating the FAQ in a few hours.

@edavidaja Great! Let's start small. Please make the change to the R Markdown file on the "dev" branch, but there's no need to rebuild the documentation (I do that myself before each release).

https://github.com/jdblischak/workflowr/blob/dev/vignettes/wflow-05-faq.Rmd

Once I've had an opportunity to actually get a demo site up and running, I can also add a vignette about private deployments.

Please check back once you have this working. I am planning on starting a new vignette on alternative deployment options, and this would be a good fit (see this comment).

I suspect 3 is slightly outside my level of package development skill, so no commitments there, but if I make it happen, I'm happy to submit that later as well.

No worries! That would be pushing my skills, too. I don't think it is necessary to build a dedicated function until there are sufficient users that are interested in hosting with AWS.

@jdblischak
Copy link
Member

The FAQ entry was added by @edavidaja in PR #124.

@edavidaja Please post to this Issue once you have a working demo, and then we can discuss the plan for more long-form workflowr-specific documentation. Thanks!

@jdblischak
Copy link
Member

@edavidaja Your documentation on hosting on AWS is now included in the official docs now that workflowr 1.2.0 has been released. I moved it to a new vignette on alternative deployment options. Thanks again for your contribution!

https://jdblischak.github.io/workflowr/articles/wflow-08-deploy.html#amazon-s3-password-protected

I'm going to close this Issue since it's been acted on. Please feel free to re-open in the future (or open a new Issue that references this old one) if you'd like to discuss adding more documentation or features.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants