
BobS
Super Moderator-
Posts
331 -
Joined
-
Last visited
Everything posted by BobS
-
Not yet. We're still working on getting the base package stable. Very few of the plug-ins and add-ons have been updated for use with 8-Coral, but we'll get there some day. If you'd like to help, we'd be happy to have your input! PM me. Regards, BobS
-
Yes, that will work for the MiniServer itself. Normally, however, we dissuade people from using paths with spaces. The problem is that we don't know whether the apps they will be hosting will tolerate any spaces. As a result, the policy is to steer clear. Regards, BobS
-
Wow! Thanks, Yoni! That should help grabby a lot. I'm still going to do this test myself, but I think you've put your finger on his problem. Regards, BobS
-
The Law of Unintended Consequences strikes again! Regards, BobS
-
First off, what VERSION of The Uniform Server are you using? This makes a BIG difference in what to look for. There are a number of factors here to look at. You "confused" things a bit by setting up both ssl AND vhosts. I've never tried that combo, so bear with me. Note that in reality, ssl is a special case vhost. It still should work. Check the vhosts portion of the httpd.conf file (at the end). This is the most likely area for the problem. Check your HOSTS file. It needs the following entry: 127.0.0.1 mysite.com Probably this is okay, depending on The Uniform Server version. I suggest that if you want to see the live site and also test with The Uniform Server that you DON'T use the exact same site name. So if your production site is mysite,com, use mysite.org, for example. I'm going to set this up on a VM to see what's needed. I'm going to use 7-Orion to begin. Regards, BobS
-
Yep. That's what the new Coral vhosts setup does for you, to some extent. You still need to be sure to specify the separate folders properly. Regards, BobS
-
It appears so. WinSrvr2008 should have VC9 files included, which is the only other library required (as I recall). Regards, BobS
-
Well, I haven't seen this particular problem. On the other hand, I initially had scripts just stop arbitrarily. What I found out was that I had to do the following: Open a command prompt; execute wscript.exe A new window will open: Windows Script Host Settings There are two options. Clear the check boxes on both. Note that this is a persistent change. You can also type wscript /? to see the help panel. This MAY resolve the popup problem, since I think that's their "logo" screen. Regards, BobS
-
Wow, I need to add that to my list of "must-haves". Regards, BobS
-
Totally believable, since 2008 has more inherent overhead. All those extra nifty features. But you bought a faster machine to go with the 2008, right? Regards, BobS
-
Not so good: APC as default PHP Accelerator
BobS replied to traxxus's topic in Uniform Server - Windows
Hmmm. Works like a charm on my WS2003R2-SP2. This would take some serious debugging. Nevertheless, maybe you're right that these shouldn't be on by default. Regards, BobS -
It's still not quite soup. I've done some very detailed testing, and I have sent the list of problems privately to Ric. He's fixing them and we'll have another release next week. Regards, BobS
-
Well, it's broken. That's all. And yes, it will work properly (we hope) in the next version. Regards, BobS
-
That's the problem when staying up too long working. Better to get some sleep! Regards, BobS
-
That depends in part on your intended sever exposure. You should use this only for testing. I suggest you download Nano-5.0, since it has the most up-to-date php 5.2 (5.2.10) included. It should work as a test bed. I don't know if that version will even work properly with 8-Coral. I know that the php.ini files would need to be updated for certain changes we have made. Regards, BobS
-
I'm having a problem with the term "Website", since it covers ALL of The Uniform Server and whatever apps you installed. That doesn't narrow it down enough for me to help. I work a bit in Spanish, and the accented characters work just fine in WordPress and other apps. So first of all, I'd need more detail on exactly what app's ADMIN account and where you're entering this information. Regards, BobS
-
Sorry this took so long to reply (lost the thread). I'm also sorry that I haven't a clue what would create these. Still not enough information. Are these file names the same as in the public folder? Why would you need .php files open to the public? I also suggest you create a duplicate site NOT ope to the public, and see if you can duplicate this. You could access it from another computer on your local LAN to simulate "external" access. Regards, BobS
-
Public Server w/DynDNS & Alternate Listen Port
BobS replied to bincho's topic in Uniform Server - Windows
Note that, as of January 2012, this list is rather dated. Several services have changed or folded. BTW, the list is in German (Google will translate). Since 5-Nano, The Uniform Server has been supporting DtDNS for DDNS resolution. Regards, BobS -
It was resolved by copying the CSS and images back to the www folder. Since there were two .htaccess files restricting access, the us_splash copy would disallow access to the css/images, while the www would allow the text. Regards. BobS
-
Thanks Ric. I've done some preliminary checking, and there are enough problems that we should not release this version. This is more a notice to others not to waste their time downloading and testing this. I'm sending you a full list by email.... Regards, BobS
-
Wow, Bill! Good catch. We really appreciate this type of response, since it makes the product better for everyone. One of the problems with skinnying-down a full program is when you go a step too far, but don't know it. Normally you catch that when testing, but that also depends on what you test for! Since Ric was using this primarily as a tutorial tool, I'll bet he never tried to open any of those mime types. BTW, for those new to the Coral-Mini, it's a stripped-downed Apache server, running on port 8081, with the bare minimum required to run CGI scripts. It includes a full tutorial on VB scripting. Regards, BobS
-
In The Uniform Server versions before 8-Coral, the method of startup is defined in UniServer\unicon\main\includes\config.inc.php. You'll see that there are two variables that control what happens at startup: $server_standard and $server_service, which are set to 7 by default. Setting these to 3 will suppress the redirect to the index pages If you read the comments in the file, it will be abundantly clear how to change these for your desired actions. Regards, BobS
-
The reason Yoni is asking, is that Coral-8.0.0 does a better job of dealing with vhosts. It's a bit clearer and covers all the bases. If you use it, BE SURE to read the associated docs. Regards, BobS
-
Great, glad to hear you got it running right. The key to the garbled page is that the CSS is in a different subdirectory from the index.php file. Because there are two different .htaccess files guarding the directories, it creates this situation. The us-splash .htaccess must allow the same access as the www .htaccess. Note that Coral-8 has ALL the docs. Use the link on the Unicontroller (Server Documentation) to get to it. We worked hard to get it accurate and complete. There are two different info pages displayed by The Uniform Server at different times. The initial splash page is called only when Apache starts (and you can modify this action). It lists the primary components and their revision numbers (manually updated, I might add). If you stop and restart Apache, you'll see the splash page again. The second is the index.php file in the server root (www), which you can initiate with the View www button. This is the one that has ad hoc links to all your subdirectories and php files. The Server configuration > General > Root www - Change passwords and access doesn't yet know about the secondary .htaccess files, like in us_spash, and we may need to just duplicate the style and images folders to resolve this mess. Regards, BobS
-
And the reason I would always say that was that we did NOT have this guide to secure against the Internet world sufficiently! It still won't change the issue of hosting management. I plan on writing a "Hardening The Uniform Server for the Internet" for the Wiki, based on this and other information. At least that way, if you want to actually open up your site to the WorldWildWeb, you can do so without leaving your machine open to compromise. If you'd like to help, send me a PM for a Wiki logon. Regards, BobS