![]() Resource for teams, and it’s on-premise, so no privacy concerns or timeĬonstraints! Slight downside though, it’s $15,000/year! Unless you qualify forĭiscounts, of course, but I’m fairly sure we don’t :) Option 3 - Self-host Have sensitive data, that’s not going to fly. You can protect it withĪ password, but that’s not the same as being on the company intranet. Second is privacy - by definition ShinyApps is public. Even at $40/month you only get 500 hours, so if your app is inĬonstant use, that’s 16hrs/day - fine if your team is in one timezone, but mine That’s perfect for testing, but not if you are building an app forĪ team to use. Month, and at the free tier it’s only 15, ShinyApps has a limited number of of “active hours” per Taking their first steps to try it! However, it has two drawbacks that mayįirstly, there’s time. It’s a great way to try Shiny out, and I encourage those ShinyApps which has a free tier, and then scaling costs Resources for hosting Shiny out there, so why would you roll your own? Option 1: ShinyAppsįor those wanting something easy and free / low-cost, then there’s Let’s start with my slides before we get to the how-to. ![]() Have been asking for the notes so that they can do it themselves, which seems Last month I was at the lovely EdinbR meetup to present my guide ![]()
0 Comments
Leave a Reply. |