digital-ocean

问题 I've just deployed my app to DigitalOcean using (Managed Database) and I'm getting the following error when calling php artisan migrate SQLSTATE[HY000]: General error: 3750 Unable to create or change a table without a primary key, when the system variable 'sql_require_primary_key' is set. Add a primary key to the table or unset this variable to avoid this message. Note that tables without a primary key can cause performance problems in row-based replication, so please consult your DBA before

问题 I am creating a New Application using Strapi and I have tried to connect it with my MongoDB which is hosted on Digital Ocean but unfortunately Strapi is not able to fetch the collections from existing MongoDB . Here, I am mentioning the complete steps that I have followed to achieve the connection of Strapi with the existing MongoDB: I have followed this guide step by step to create a Strapi Application: Quick_Start_Strapi Although, I need to connect to my existing MongoDB which is hosted on

问题 We have GD Library installed on DigitalOcean's Litespeed server, however, it does not support WebP. I'd like to enable WebP support. 回答1: This is on LiteSpeed' Engineer's to-do list but there is no ETA. I know it doesn't sound like an answer, but you can either just wait for it or build it yourself. 来源： https://stackoverflow.com/questions/61574434/enabling-webp-support-in-gd-library-on-ubuntu-18-04-running-on-litespeed

问题 We have GD Library installed on DigitalOcean's Litespeed server, however, it does not support WebP. I'd like to enable WebP support. 回答1: This is on LiteSpeed' Engineer's to-do list but there is no ETA. I know it doesn't sound like an answer, but you can either just wait for it or build it yourself. 来源： https://stackoverflow.com/questions/61574434/enabling-webp-support-in-gd-library-on-ubuntu-18-04-running-on-litespeed

问题 I've been attempting to setup my built-up Django Instance as a Database Server. Had chosen DigitalOcean as my platform and had read that Dokku is a useful PaaS system that will enable better scalability for this API I'm trying to deploy. I have been at this problem for the last 3-4 days straight and really had gone through every potential means of solution I could have found online. Being more of a front-end developer, I'm pretty bad at this backend installation matter. At first I thought

问题 I have a single page application written with vuejs and i want to deploy the application using digitalocean, nginx and docker my question is, what do i need to add to the config file/docker file to make that the app will use https and not http? (i'm going to use self signed certificates) yes, i searched the question already, but nothing seems to work with that template. also, the backend for this app is nodejs with express that will be on different container on the same digital ocean server

问题 So I've decided to set up my project with two droplets, a MongoDB image droplet and a NodeJS image droplet. I did so to make it easier to scale both droplets in the future, and other applications may be connecting to the DB in the future, both on Ubuntu 18.04. I'm getting the error of: Could not connect to the database: { MongooseServerSelectionError: connection timed out at new MongooseServerSelectionError (/root/eternal-peace-code/node_modules/mongoose/lib/error/serverSelection.js:22:11) at

问题 I am deploying my web application at DigitalOcean. My environment is: Ubuntu 18.04, PHP + FPM 7.3, NGINX. My routing system is based on the $_SERVER PATH_INFO, but it only returns empty, so I can't access my routes. I already researched the solution and none of StackOverflow worked for me. My default file in /etc/nginx/sites-enabled is: server { listen 80; listen [::]:80; root /usr/share/nginx/my-site/public; index index.php index.html index.htm; server_name localhost; location / { try_files

问题 I'm calling my express route (domain.com/api) from another domain (domain1.com). So I've set up Express to accept POST requests to the route /api and signing a JWT before exchanging the JWT via Axios for a Bearer access token. I cannot seem to get the Axios post request to fire. Is is possible it's a firewall thing? How can I see where the error lives? Forgive me, I'm still new to Node/Express. Here is my pertinent code: const express = require('express'); const cors = require("cors"); const

问题 I recently followed a video chat tutorial and wanted to host it on Digitalocean to test some webRTC things. I got it working and even got it hosted on Heroku. However, when I go to host it on an unused droplet (running off of the initial $100 free Digitalocean credit) and SSH into my droplet & run npm start (yes, although its not in the tutorials github code, npm start is in the package.json ), I get an error. USER***@nodejs-s-1vcpu-1gb-sfo2-01:~/DIRNAME$ sudo npm start > livestream-server@0