![]() Troubleshoot server performance problems.Enable SSL access over HTTPS with Cloudflare.Understand the message "AWS instance scheduled for retirement".Modify the AWS instance type or CPU/memory configuration. ![]() Auto-configure a Let's Encrypt certificate.Manage Bitnami Launchpad instances through the AWS Console.Launch T2, C4 or M4 AWS instances using the Bitnami Launchpad for AWS Cloud.Install and use the Amazon CloudWatch agent.Give SSH access to another person, such as a customer.Learn about the Bitnami Configuration Tool.Move AWS instances between the AWS Console and the Bitnami Launchpad for AWS Cloud.Configure third-party SMTP for outbound emails.Reassociate an existing IP address with a new AWS instance.Understand what data Bitnami collects from deployed Bitnami stacks.Learn about Bitnami PHP application modules deprecation.Understand the default directory structure.Learn about the SSH warning 'REMOTE HOST IDENTIFICATION HAS CHANGED'. ![]() What even puzzling me is, how NextCloud has implemented this nearly two years ago, and ownCloud is still considering to do this or not. Regardless of which situation, this type of limit (and few others), really make me think the ownCloud target audience isn't for what aforementioned, but instead smaller Cloud reseller. Made a decision of sync over my Android phone using Folder sync, after 8000+ images, realize it was impossible to use now as ownCloud app can never finish generating the Thumbnail. For one, copy over the images manually (without OC), another sync mass images without the OC due to performance factors. I have so many self scenario that a simple OCC command line for admins to do background thumbnail generating at their own freewill will work out better than ondemand generation. People who like more flexibility and control.Decision over it should be opex (Cloud based) or capex (self host solution).The reason can simply be, but not limited to: I believe ownCloud is best suit target at the audience of people who choose not their data over public cloud offering, whether it Dropbox, LiveDrive, Sharepoint, etc. I sincerely think the target of 'ownCloud' audience is loosing its plot along the way. So this needs careful 5-years, still a milestone of 'maybe someday' goal. On server with 100k users it is likely that such background job would take ages to finish and consume a lot of CPU on many servers. Now I'm not aware of any timeline to provide such background job. ![]() I think this is a good prerequisite for a future background job for preview generation, because said job could then simply build previews for all these fixed supported sizes. So the viewer would pick the preview with the closest size instead of requesting a preview with the exact size from the server. This app implements the previews with fixed scales instead of expecting previews with every possible pixel size. In any case, I don't think that's the right direction and we should stay in PHP-world to keep the easy of deployment for everyone.Ĭurrently we're reworking the frontend and integrating both the video player and slideshow view into a single app, see (release coming soon). Maybe it needs an OC app that is able to call it with shell_exec. Now in 2019 I'm still unsure if / how to incorporate such external tool in a way to make it work from OC. [ "$(id -un)" = "$/268/200 > /dev/nullĭone <<< the reason this was likely never incorporated back then is because the design goals of ownCloud was to be purely PHP to make sure that everyone can deploy this on their shared hosters, etc. OC_FOLDER='path/within/your/owncloud/webinterface'
0 Comments
Leave a Reply. |