Smalltalk › Pharo › Pharo Smalltalk Developers

http://pharo.org/files/pharo.png

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

9 messages Options

Sven Van Caekenberghe-2

http://pharo.org/files/pharo.png

Who removed http://pharo.org/files/pharo.png ?

Why ?

It is used in tests/examples.

Could it be put back please, even it is not used (it does do no harm) ?

A basic rule of the Web is not to break existing stuff.

Sven

stepharo

Re: http://pharo.org/files/pharo.png

No idea but it should not because it breaks our nice examples.

if you have the file I can add it back.

May be esteban when he was removing Amber dependencies in Marina.

Stef

Le 6/11/16 à 18:14, Sven Van Caekenberghe a écrit :
> Who removed http://pharo.org/files/pharo.png ?
>
> Why ?
>
> It is used in tests/examples.
>
> Could it be put back please, even it is not used (it does do no harm) ?
>
> A basic rule of the Web is not to break existing stuff.
yes but there is no become/allInstances to find who is using you
>
> Sven
>
>

Sven Van Caekenberghe-2

Re: http://pharo.org/files/pharo.png

On 6 Nov 2016, at 18:47, stepharo <[hidden email]> wrote:

No idea but it should not because it breaks our nice examples.

if you have the file I can add it back.

I think it is this one (a transparent png) :

But I am not 100% sure.

May be esteban when he was removing Amber dependencies in Marina.

Stef

Le 6/11/16 à 18:14, Sven Van Caekenberghe a écrit :
Who removed http://pharo.org/files/pharo.png ?

Why ?

It is used in tests/examples.

Could it be put back please, even it is not used (it does do no harm) ?

A basic rule of the Web is not to break existing stuff.
yes but there is no become/allInstances to find who is using you

Sven

EstebanLM

Re: http://pharo.org/files/pharo.png

In reply to this post by Sven Van Caekenberghe-2

It is not removed… I moved the backend from amber to seaside and there is a problem because standard installation of seaside uses /files to his own file server.

now, I want to move that but I didn’t had the time.

In the mean time, in fact real address of that file was before and still is: https://pharo.org/web/files/pharo.png

and file can still be found there.

I’m sorry if I messes up something, but I see no reason to be so upset… we all make mistakes time to time :P

Esteban

On 6 Nov 2016, at 18:14, Sven Van Caekenberghe <[hidden email]> wrote:

Who removed http://pharo.org/files/pharo.png ?

Why ?

It is used in tests/examples.

Could it be put back please, even it is not used (it does do no harm) ?

A basic rule of the Web is not to break existing stuff.

Sven

Sven Van Caekenberghe-2

Re: http://pharo.org/files/pharo.png

I am not upset, but you did not explain what you did up until now.

Still, this URL was/is used everywhere as an example (in comments and books) and tests.

It looks silly if we break our own links. And a year or so ago I already changed all those links once. If I have to do it again, I will move everything away from infrastructure that I cannot control myself.

> On 6 Nov 2016, at 19:02, Esteban Lorenzano <[hidden email]> wrote:
>
> It is not removed… I moved the backend from amber to seaside and there is a problem because standard installation of seaside uses /files to his own file server.
> now, I want to move that but I didn’t had the time.
> In the mean time, in fact real address of that file was before and still is: https://pharo.org/web/files/pharo.png
> and file can still be found there.
>
> I’m sorry if I messes up something, but I see no reason to be so upset… we all make mistakes time to time :P
>
> Esteban
>
>> On 6 Nov 2016, at 18:14, Sven Van Caekenberghe <[hidden email]> wrote:
>>
>> Who removed http://pharo.org/files/pharo.png ?
>>
>> Why ?
>>
>> It is used in tests/examples.
>>
>> Could it be put back please, even it is not used (it does do no harm) ?
>>
>> A basic rule of the Web is not to break existing stuff.
>>
>> Sven
>>
>

EstebanLM

Re: http://pharo.org/files/pharo.png

> On 6 Nov 2016, at 19:17, Sven Van Caekenberghe <[hidden email]> wrote:
>
> I am not upset, but you did not explain what you did up until now.
>
> Still, this URL was/is used everywhere as an example (in comments and books) and tests.
>
> It looks silly if we break our own links. And a year or so ago I already changed all those links once. If I have to do it again, I will move everything away from infrastructure that I cannot control myself.

I didn’t know I was breaking anything… otherwise I would have fixed it, is not that I looked at it and I said “hey, let’s break this… who cares?”
Now, I need to fix it… as many other things that we may break without knowing… that’s why I said, and I repeat: “we all make mistakes time to time”.

Esteban

>
>> On 6 Nov 2016, at 19:02, Esteban Lorenzano <[hidden email]> wrote:
>>
>> It is not removed… I moved the backend from amber to seaside and there is a problem because standard installation of seaside uses /files to his own file server.
>> now, I want to move that but I didn’t had the time.
>> In the mean time, in fact real address of that file was before and still is: https://pharo.org/web/files/pharo.png
>> and file can still be found there.
>>
>> I’m sorry if I messes up something, but I see no reason to be so upset… we all make mistakes time to time :P
>>
>> Esteban
>>
>>> On 6 Nov 2016, at 18:14, Sven Van Caekenberghe <[hidden email]> wrote:
>>>
>>> Who removed http://pharo.org/files/pharo.png ?
>>>
>>> Why ?
>>>
>>> It is used in tests/examples.
>>>
>>> Could it be put back please, even it is not used (it does do no harm) ?
>>>
>>> A basic rule of the Web is not to break existing stuff.
>>>
>>> Sven
>>>
>>
>
>

Sven Van Caekenberghe-2

Re: http://pharo.org/files/pharo.png

> On 6 Nov 2016, at 22:04, Esteban Lorenzano <[hidden email]> wrote:
>
>>
>> On 6 Nov 2016, at 19:17, Sven Van Caekenberghe <[hidden email]> wrote:
>>
>> I am not upset, but you did not explain what you did up until now.
>>
>> Still, this URL was/is used everywhere as an example (in comments and books) and tests.
>>
>> It looks silly if we break our own links. And a year or so ago I already changed all those links once. If I have to do it again, I will move everything away from infrastructure that I cannot control myself.
>
> I didn’t know I was breaking anything… otherwise I would have fixed it, is not that I looked at it and I said “hey, let’s break this… who cares?”
> Now, I need to fix it… as many other things that we may break without knowing… that’s why I said, and I repeat: “we all make mistakes time to time”.

OK, of course you did not do this on purpose. And it is good that you maintain the main website.

Now, it is common/good practice to front Seaside with nginx (or apache). If you do, you can export the Seaside files to the file system (using #deployFiles) to serve them faster/better when found. Like this:

upstream my-seaside {
ip_hash;
server localhost:9090;
...
}

server {
...

location /files {
alias /home/pharo/my-files;
try_files $uri @seaside;
gzip on;
gzip_types application/x-javascript text/css;
expires 30d;
}

location / {
proxy_pass http://my-seaside;
add_header X-Server Pharo;
}

location @seaside {
proxy_pass http://my-seaside;
add_header X-Server Pharo;
}
}

With this scheme you should be able to add any statically served file manually. (Here only under /files, but you could add more handlers).

Sven

> Esteban
>
>>
>>> On 6 Nov 2016, at 19:02, Esteban Lorenzano <[hidden email]> wrote:
>>>
>>> It is not removed… I moved the backend from amber to seaside and there is a problem because standard installation of seaside uses /files to his own file server.
>>> now, I want to move that but I didn’t had the time.
>>> In the mean time, in fact real address of that file was before and still is: https://pharo.org/web/files/pharo.png
>>> and file can still be found there.
>>>
>>> I’m sorry if I messes up something, but I see no reason to be so upset… we all make mistakes time to time :P
>>>
>>> Esteban
>>>
>>>> On 6 Nov 2016, at 18:14, Sven Van Caekenberghe <[hidden email]> wrote:
>>>>
>>>> Who removed http://pharo.org/files/pharo.png ?
>>>>
>>>> Why ?
>>>>
>>>> It is used in tests/examples.
>>>>
>>>> Could it be put back please, even it is not used (it does do no harm) ?
>>>>
>>>> A basic rule of the Web is not to break existing stuff.
>>>>
>>>> Sven

EstebanLM

Re: http://pharo.org/files/pharo.png

sorry for taking so long… yesterday I had a mess in my head with different stuff.

I added the correct redirect and now http://pharo.org/files/pharo.png answers correct file (I just added a redirect rule as this was the easiest/way to fix this problem).

Esteban

On 6 Nov 2016, at 23:10, Sven Van Caekenberghe <[hidden email]> wrote:

On 6 Nov 2016, at 22:04, Esteban Lorenzano <[hidden email]> wrote:

On 6 Nov 2016, at 19:17, Sven Van Caekenberghe <[hidden email]> wrote:

I am not upset, but you did not explain what you did up until now.

Still, this URL was/is used everywhere as an example (in comments and books) and tests.

It looks silly if we break our own links. And a year or so ago I already changed all those links once. If I have to do it again, I will move everything away from infrastructure that I cannot control myself.

I didn’t know I was breaking anything… otherwise I would have fixed it, is not that I looked at it and I said “hey, let’s break this… who cares?”
Now, I need to fix it… as many other things that we may break without knowing… that’s why I said, and I repeat: “we all make mistakes time to time”.

OK, of course you did not do this on purpose. And it is good that you maintain the main website.

Now, it is common/good practice to front Seaside with nginx (or apache). If you do, you can export the Seaside files to the file system (using #deployFiles) to serve them faster/better when found. Like this:

upstream my-seaside {
ip_hash;
server localhost:9090;
...
}

server {
...

location /files {
   alias /home/pharo/my-files;
   try_files $uri @seaside;
   gzip on;
   gzip_types application/x-javascript text/css;
   expires 30d;
}

location / {
   proxy_pass http://my-seaside;
   add_header X-Server Pharo;
}

location @seaside {
   proxy_pass http://my-seaside;
   add_header X-Server Pharo;
}
}

With this scheme you should be able to add any statically served file manually. (Here only under /files, but you could add more handlers).

Sven

Esteban

On 6 Nov 2016, at 19:02, Esteban Lorenzano <[hidden email]> wrote:

It is not removed… I moved the backend from amber to seaside and there is a problem because standard installation of seaside uses /files to his own file server.
now, I want to move that but I didn’t had the time.
In the mean time, in fact real address of that file was before and still is: https://pharo.org/web/files/pharo.png
and file can still be found there.

I’m sorry if I messes up something, but I see no reason to be so upset… we all make mistakes time to time :P

Esteban

On 6 Nov 2016, at 18:14, Sven Van Caekenberghe <[hidden email]> wrote:

Who removed http://pharo.org/files/pharo.png ?

Why ?

It is used in tests/examples.

Could it be put back please, even it is not used (it does do no harm) ?

A basic rule of the Web is not to break existing stuff.

Sven

Sven Van Caekenberghe-2

Re: http://pharo.org/files/pharo.png

Super, thank you Esteban!

> On 8 Nov 2016, at 13:26, Esteban Lorenzano <[hidden email]> wrote:
>
> sorry for taking so long… yesterday I had a mess in my head with different stuff.
> I added the correct redirect and now http://pharo.org/files/pharo.png answers correct file (I just added a redirect rule as this was the easiest/way to fix this problem).
>
> Esteban
>
>> On 6 Nov 2016, at 23:10, Sven Van Caekenberghe <[hidden email]> wrote:
>>
>>
>>> On 6 Nov 2016, at 22:04, Esteban Lorenzano <[hidden email]> wrote:
>>>
>>>>
>>>> On 6 Nov 2016, at 19:17, Sven Van Caekenberghe <[hidden email]> wrote:
>>>>
>>>> I am not upset, but you did not explain what you did up until now.
>>>>
>>>> Still, this URL was/is used everywhere as an example (in comments and books) and tests.
>>>>
>>>> It looks silly if we break our own links. And a year or so ago I already changed all those links once. If I have to do it again, I will move everything away from infrastructure that I cannot control myself.
>>>
>>> I didn’t know I was breaking anything… otherwise I would have fixed it, is not that I looked at it and I said “hey, let’s break this… who cares?”
>>> Now, I need to fix it… as many other things that we may break without knowing… that’s why I said, and I repeat: “we all make mistakes time to time”.
>>
>> OK, of course you did not do this on purpose. And it is good that you maintain the main website.
>>
>> Now, it is common/good practice to front Seaside with nginx (or apache). If you do, you can export the Seaside files to the file system (using #deployFiles) to serve them faster/better when found. Like this:
>>
>> upstream my-seaside {
>> ip_hash;
>> server localhost:9090;
>> ...
>> }
>>
>> server {
>> ...
>>
>> location /files {
>> alias /home/pharo/my-files;
>> try_files $uri @seaside;
>> gzip on;
>> gzip_types application/x-javascript text/css;
>> expires 30d;
>> }
>>
>> location / {
>> proxy_pass http://my-seaside;
>> add_header X-Server Pharo;
>> }
>>
>> location @seaside {
>> proxy_pass http://my-seaside;
>> add_header X-Server Pharo;
>> }
>> }
>>
>> With this scheme you should be able to add any statically served file manually. (Here only under /files, but you could add more handlers).
>>
>> Sven
>>
>>> Esteban
>>>
>>>>
>>>>> On 6 Nov 2016, at 19:02, Esteban Lorenzano <[hidden email]> wrote:
>>>>>
>>>>> It is not removed… I moved the backend from amber to seaside and there is a problem because standard installation of seaside uses /files to his own file server.
>>>>> now, I want to move that but I didn’t had the time.
>>>>> In the mean time, in fact real address of that file was before and still is: https://pharo.org/web/files/pharo.png
>>>>> and file can still be found there.
>>>>>
>>>>> I’m sorry if I messes up something, but I see no reason to be so upset… we all make mistakes time to time :P
>>>>>
>>>>> Esteban
>>>>>
>>>>>> On 6 Nov 2016, at 18:14, Sven Van Caekenberghe <[hidden email]> wrote:
>>>>>>
>>>>>> Who removed http://pharo.org/files/pharo.png ?
>>>>>>
>>>>>> Why ?
>>>>>>
>>>>>> It is used in tests/examples.
>>>>>>
>>>>>> Could it be put back please, even it is not used (it does do no harm) ?
>>>>>>
>>>>>> A basic rule of the Web is not to break existing stuff.
>>>>>>
>>>>>> Sven
>>
>>
>