Krydos

I tested python3.6 django writing to a file on Tommy and it works for me. You have to create the log file manually and give it 666 permissions. 666 means owner, group, and other can read/write from it. You have to remember that django runs as the user nobody not your hosting account user so if you use the default 644 permissions nobody won't have access to write to it.

You said you wanted it on juanch0.heliohost.org There you go https://niandubay.tk/test.aspx

The easiest way to do anything django related is to develop on your home computer, migrate and all that locally. What I do is enable remote database connection and then have both the local and server version of django use the host tommy.heliohost.org. That way whether you're testing it on your home computer or running it on the server it uses the same database.

The version of mediawiki that we're using came out in 2012. I think it'll survive another couple days. Take your time.

There you go http://juanch0.heliohost.org/test.aspx

Failed FTP logins. Unblocked.

wiki.helionet.sql is located at /home/bailey/ The cleanup script didn't help a lot. It's still 275 mb. Let us know if you need help. Just create wiki.bailey.heliohost.org or whatever you want. Once you get it working and upgraded I can transfer it to Cody.

You're going to install/upgrade it on your Tommy account.

It's working now.

What he means is the queued page has a tendency to get cached in your browser. Browsers sometimes refuse to load the data from a website because they want to pretend they're faster than they are. If you clear your browser cache you force the browser to show your actual website not an old stale version saved on your hard drive.

How about I provide a dump of the wiki database, and one of you install/upgrade it on your account? Bailey, you want to do this? Let me know and I'll put the wiki's database dump on your account. The wiki database dump was 375 MB mostly because of all the spam accounts that have been created over the years. I'm running a script to delete all of the accounts that have never made an edit to clean things up.

As long as your vpn doesn't constantly cycle through IPs it will work. You can also use a web proxy.

For instance, there is someone on the same server as you that used 254% more bandwidth, and you still did 293% more load. There you go http://faucet.heliohost.org/

Unblocked. No, that wouldn't work because you don't have access to whm.

There you go http://sheshiresat.heliohost.org/

Deployed. http://ganeshpi.heliohost.org/ganeshpi/ Since you're on Johnny is can take up to 24 hours to start working. In the meantime it will show 404.

You should have said something sooner. I just installed Ubuntu 17 on my new laptop last night.

Most people deploy like blog.war or test.war.

Neither of those are database errors though. The top one is just a warning, but the code should still execute fine for now. It's just letting you know that when php is upgraded it will probably stop working. The second error is just some plugin of yours complaining about not being able to write to a file. It's not a database issue either. I took a look at your error_log and I found this [15-Oct-2017 12:59:05 UTC] WordPress errore sul database Table 'maicol07_wpmk.wp_datalist' doesn't exist per la query SELECT count(*) FROM `wp_datalist` WHERE `url` = "/wp-cron.php?doing_wp_cron=1508072344.5565590858459472656250" fatta da require_once('wp-load.php'), require_once('wp-config.php'), require_once('wp-settings.php'), include('/themes/Gameleon/functions.php') That's a database error and it looks like your wordpress database is missing a table. Not sure how that would have happened.

I have another idea for you. Rather than your visual basic program connecting directly to the database, why not have your program connect to a php file and the php file can connect to the database? Php actually knows how to close mysql connections.

Does it work now? I think it's because your .war file has a kind of a ridiculous name.

You can deploy your own .war at https://tommy.heliohost.org:2083/frontend/paper_lantern/java/index.live.php

Done.

Yes, there is no limit to the number of IPs that can connect to a database. The limitation is on the maximum number of simultaneous open connections regardless of what IP or localhost they come from.

That error could mean a lot of things. Is there any more informative error in your error_log file?