I've done the first of two parts. I've changed the config file nginx.conf to proxy to the running image. [1] In strict terms, since the port number has been removed (i.e. It is no no longer box4.squeak.org:8624) the image is deployed. Unfortunately, without a "www" subdomain or no subdomain (i.e. http://squeak.org) not many people are going to find it. Thus I now turn to tinydns. When that's done, it's deployed.
Chris
[1]
I copied default.conf into default.conf_master.
I then hacked default.conf, which now contains only:
server { listen 80; server_name *.squeak.org;
location / {
proxy_pass http://127.0.0.1:8624; }
}
Congrats, you can test it already with http://new.squeak.org/ .
Note that the primary complication with changing DNS so that http://squeak.org/ will work is going to be not breaking email working for squeak.org. Moral: when you think you are done test email.
Ken
On 03/11/2014 08:59 AM, Chris Cunnington wrote:
I've done the first of two parts. I've changed the config file nginx.conf to proxy to the running image. [1] In strict terms, since the port number has been removed (i.e. It is no no longer box4.squeak.org:8624) the image is deployed. Unfortunately, without a "www" subdomain or no subdomain (i.e. http://squeak.org) not many people are going to find it. Thus I now turn to tinydns. When that's done, it's deployed.
Chris
[1]
I copied default.conf into default.conf_master.
I then hacked default.conf, which now contains only:
server { listen 80; server_name *.squeak.org;
location / { proxy_pass http://127.0.0.1:8624; }
}_______________________________________________ Webteam mailing list Webteam@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/webteam
On Mar 11, 2014, at 10:07 AM, Ken Causey ken@kencausey.com wrote:
Congrats, you can test it already with http://new.squeak.org/ .
Thank you very much. Your approval in this process is important to me.
Note that the primary complication with changing DNS so that http://squeak.org/ will work is going to be not breaking email working for squeak.org. Moral: when you think you are done test email.
I'll test email. I was thinking I might inadvertently shutter map, wiki, and source -- all on box2. I'll check email too. As Han Solo said: "This could be a real short trip."
Ken
On 03/11/2014 08:59 AM, Chris Cunnington wrote:
I've done the first of two parts. I've changed the config file nginx.conf to proxy to the running image. [1] In strict terms, since the port number has been removed (i.e. It is no no longer box4.squeak.org:8624) the image is deployed. Unfortunately, without a "www" subdomain or no subdomain (i.e. http://squeak.org) not many people are going to find it. Thus I now turn to tinydns. When that's done, it's deployed.
Chris
[1]
I copied default.conf into default.conf_master.
I then hacked default.conf, which now contains only:
server { listen 80; server_name *.squeak.org;
location / { proxy_pass http://127.0.0.1:8624; }
}_______________________________________________ Webteam mailing list Webteam@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/webteam
Webteam mailing list Webteam@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/webteam
Great progress on the new website. I have a few suggestions. Hope you don't mind.
The ttl of all DNS records should be at most 3600 until the system is considered stable. The current value is 86400 (1 day), so you'll have to wait more than a day till any change takes effect for everyone. We even keep it at a low value (3600-7200) for production systems, because it's really helpful when something goes wrong.
Some old DNS records were not kept (e.g. box2.squeak.org, bugs.squeak.org, map.squeak.org, ftp.squeak.org , etc). It would be worth restoring these until the services are migrated. For example squeakmap and mantis, or the downloads don't work at the moment.
Serving the static files (images, scripts) for the website needs a permanent solution. We want to let the browsers and proxies to cache these, but not the dynamically generated pages. There are many different ways to solve it, each having their pros and cons.
I can help with configuring nginx. Let me know if you need it.
Levente
On Tue, 11 Mar 2014, Ken Causey wrote:
Congrats, you can test it already with http://new.squeak.org/ .
Note that the primary complication with changing DNS so that http://squeak.org/ will work is going to be not breaking email working for squeak.org. Moral: when you think you are done test email.
Ken
On 03/11/2014 08:59 AM, Chris Cunnington wrote:
I've done the first of two parts. I've changed the config file nginx.conf to proxy to the running image. [1] In strict terms, since the port number has been removed (i.e. It is no no longer box4.squeak.org:8624) the image is deployed. Unfortunately, without a "www" subdomain or no subdomain (i.e. http://squeak.org) not many people are going to find it. Thus I now turn to tinydns. When that's done, it's deployed.
Chris
[1]
I copied default.conf into default.conf_master.
I then hacked default.conf, which now contains only:
server { listen 80; server_name *.squeak.org;
location / { proxy_pass http://127.0.0.1:8624; }
}_______________________________________________ Webteam mailing list Webteam@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/webteam
On Mar 11, 2014, at 5:11 PM, Levente Uzonyi leves@elte.hu wrote:
Great progress on the new website. I have a few suggestions. Hope you don't mind.
The ttl of all DNS records should be at most 3600 until the system is considered stable. The current value is 86400 (1 day), so you'll have to wait more than a day till any change takes effect for everyone. We even keep it at a low value (3600-7200) for production systems, because it's really helpful when something goes wrong.
I'll look into that. It's a detail I hadn't thought of. Obvious when you say it, though.
Some old DNS records were not kept (e.g. box2.squeak.org, bugs.squeak.org, map.squeak.org, ftp.squeak.org , etc). It would be worth restoring these until the services are migrated. For example squeakmap and mantis, or the downloads don't work at the moment.
Hmm, yea. I was afraid of this. It'll get sorted.
Serving the static files (images, scripts) for the website needs a permanent solution. We want to let the browsers and proxies to cache these, but not the dynamically generated pages. There are many different ways to solve it, each having their pros and cons.
I can help with configuring nginx. Let me know if you need it.
That would be great. I'll start to cross post with the box-team list. OK, it already is. Tomorrow, I'll start to make a list of things that need fixing. And I'll dig up details to go with the list. Anything you have to say about how better configure things, I'm happy to hear. That would be of great assistance.
Chris
Levente
I just sent Levente information to get started in box4. I plan to steer clear of that box for the next few hours for reasons that will be obvious to him.
I nominate Levente to be the box team leader. Can I get a second?
Chris
1. http://build.squeak.org works fine as it's on box3. The problem is in box2, specifically in the /tinydns/root/data.in file that I changed yesterday.
2. The plan I have to fix this is to change the TTL to one hour and iterate. The problem is the wildcard which did duty for many subdomains reaching box2.
3. I count those subdomains to be: ftp, bugs, source, wiki, map, www, nil, news, and lists.
4. I intend to remove the wildcard and state each subdomain explicitly. The current state of the tinydns file is attached [1]
5. For future reference the way tinydns works is as follows. Edit the data (or data.in) file and execute make. This produces a fresh data.cdb file, which takes effect immediately. tinydns need not be restarted.
6. The /tinywiki/root/Makefile in box4 compiles the data.cdb file and then rsync's a copy to box3. There is no such relationship to box2, I don't think. At least from reading the Makefiles in boxes 2 and 4.
7. I apologize for stopping the squeak rig in its tracks. The fault is mine. And as I have taken the blame, I feel free to say that this setup is a kludge.
8. I think there is no chance of the email knocking out, as it's on the lists subdomain on squeakfoundation.org, which I have no need to touch. It should continue to work as expected.
Thank you for your patience,
Chris
[1]
# SqueakFoundation.org .squeakfoundation.org:85.10.195.197:a .squeakfoundation.org:69.72.148.198:b +squeakfoundation.org:85.10.195.197 +*.squeakfoundation.org:85.10.195.197
+box2.squeakfoundation.org:85.10.195.197 +lists.squeakfoundation.org:85.10.195.197 @lists.squeakfoundation.org:85.10.195.197:box2.squeakfoundation.org Cmap1.squeakfoundation.org:map.squeak.org
# Squeak.org .squeak.org:85.10.195.197:a.ns.squeakfoundation.org .squeak.org:69.72.148.198:b.ns.squeakfoundation.org +squeak.org:85.10.195.197 +*.squeak.org:85.10.195.197
# Box3 at Gandi.net via SFC October 2012 +box3.squeak.org:173.246.101.237 +build.squeak.org:173.246.101.237
# Box4 at Gandi.net via SFC December 2012 +box4.squeak.org:173.246.104.42 +www.squeak.org:173.246.104.42
Is there some reason to have so many non-Squeak projects on the "Projects" page?
Amber? Pharo? LivelyKernel? Cuis? U8? Although some of these may be "inspired" by, none of them are developed in Squeak.
And yet, actual Squeak projects are missing like muO, Altitude, Magma and more.
I want to join the webteam and make a difference here. Is that okay?
On Tue, Mar 11, 2014 at 8:59 AM, Chris Cunnington websela@yahoo.com wrote:
I've done the first of two parts. I've changed the config file nginx.conf to proxy to the running image. [1] In strict terms, since the port number has been removed (i.e. It is no no longer box4.squeak.org:8624) the image is deployed. Unfortunately, without a "www" subdomain or no subdomain (i.e. http://squeak.org) not many people are going to find it. Thus I now turn to tinydns. When that's done, it's deployed.
Chris
[1]
I copied default.conf into default.conf_master.
I then hacked default.conf, which now contains only:
server { listen 80; server_name *.squeak.org;
location / { proxy_pass http://127.0.0.1:8624; }
}_______________________________________________ Webteam mailing list Webteam@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/webteam
On Mar 11, 2014, at 10:31 AM, Chris Muller asqueaker@gmail.com wrote:
Is there some reason to have so many non-Squeak projects on the "Projects" page?
So remove them.
Amber? Pharo? LivelyKernel? Cuis? U8? Although some of these may be "inspired" by, none of them are developed in Squeak
It's your site, make the changes you want.
And yet, actual Squeak projects are missing like muO, Altitude, Magma and more.
I want to join the webteam and make a difference here. Is that okay?
Absolutely.
But for you to see where I'm at right now, let me quote from "The Seven Samurai": It's folly to worry about your beard, when you're in danger of losing your head.
If I muck up the dns, you'll know. We will disappear from the cyberspace like a Klingon warbird. Let me focus on that for the next few hours.
Chris
webteam@lists.squeakfoundation.org