April 2021 - Pharo-users - lists.pharo.org

Re: Whats the easiest/cheapest way to run a Pharo web app in 2021?

by Tim Mackinnon

Adding some thoughts to my own post - I have experimented with dockerize.io and so far the $2 plan (which so far I haven't been charged for) has been quite adequate for hosting something simple (and I suspect the $5 plan would do the trick as well). It does get a bit more pricey when you add a database and unlimited traffic (60GB MySQL Database: 4GB, 1000m + no traffic + 60GB persistance + 100 mb logs = $26/m) - but even then thats pretty good. It was relatively easy to do (doesn't have native Github integration yet, but has a cli for easy deployment) , and given what Esteban mentioned of his experience - this seems worth pursuing for ease of deployment/maintenance. I did find Pablo's instructions were a bit limited - in particular covering a private repo (and how Pharo and the BA docker image give no output on credential failure - I've raised an issue on BA github, but may be a pharo thing - not yet sure - but it is quite easy to overcome). It also doesn't cover safe credential storage and best practices etc. (so hopefully a future article from someone more experienced in this?) I'm curious if others have experienced anything similar they can share? I am a bit nervous the dockerize.io has little history (been around since 2019 allegedly) - but for my experimentation its fine. Others may need more, and I'm wondering where to help document this as deployment is a big stumbling block - that we actually can handle quite well with recent tooling. In this vein - I wonder where SmalltalkCI sits? Do you need it for a plain Pharo app - you just need to grep the output of Metacello and your test runner - but perhaps it does this better (I can see the need for building multiple platforms etc). Tim On Fri, 2 Apr 2021, at 10:32 AM, Tim Mackinnon wrote: > Thanks Sanjay - you have reminded me that I have some similar notes somewhere (now located) that did the command line foo to get things running - looking at mine there was quite a big of dance to provide a way to gracefully stop and start the image so that you can easily and automatically redeploy your changes (read: use Github actions or Gitlab CI). > > So Iâm curious on whether Docker is now sufficiently stable stable/easy/cheap to make it a viable alternative - and whether that is also cost efficient. > > Pablo wrote a recent blog post on running Pharo in Docker using the BA images - https://thepharo.dev/2021/02/24/running-pharo-9-in-docker/ - but while easy on the surface, if anything goes wrong - there seems to be very little debug output to know what has happened (Iâll post separately on this - as Iâm looking at comparing options here). > > With Docker options, I notice that dockerize.io (not used, just a quick search) - has a micro plan for $2/m - but is 500mb ram enough (there is a $5 one for 1gm ram). > > Or - I stick with DigitalOcean and roll my own like before - and perhaps that has got a bit simpler. > > Iâm still curious what the wider community is doing. > > > Tim > >> On 2 Apr 2021, at 05:43, Sanjay Minni <sm(a)planage.com> wrote: >> >> Hi Tim >> >> Here are my notes on installing Pharo in a DigitalOcean Ubuntu droplet. >> I usually go thru a Windows Command prompt box having installed xfec4 in the ubuntu droplet, but the command line connect and graphical remote may be easier for a Linux users. my ssh public key is also in the DO droplet >> Now the first step for me is a installing Pharo launcher thru command line and then everything is thru graphical interface >> >> Installing and checking Pharo-Launcher, Installing Pharo 8 64 bit from pharo.org (instructions as on Pharo.org <http://pharo.org/>) >> 1. In Windows 10 command prompt connect thru > ssh root@<Droplet-ip> >> 2. cd >> 3. curl -o pharo-launcher.zip -L https://files.pharo.org/pharo-launcher/linux64 >> 4. unzip pharo-launcher.zip >> or thru the GUI-> extract here >> (pharo-launcher files will be extracted in ./pharo-launcher) >> Now while connected to the linux graphical interface thru windows remote terminal and in the GUI >> 5. Create a icon on desktop thru right-click âCreate Launcherâ for pharo-launcher >> 6. Create pharo images thru pharo-launcher >> >> hope this is of use >> >> Sanjay Minni >> >> On Thu, 1 Apr 2021 at 16:31, Tim Mackinnon <tim(a)testit.works> wrote: >>> Hi everyone - its been a few year since I last hosted a little Pharo web app - and the last time I did, Sven pointed me to DigitalOcean and creating a tiny instance and configuring an Ubuntu server and then copying a pharo image on to that. It recall it wasnât too bad, albeit a bit fiddlyâ¦ >>> >>> Now several years later - I canât recall the exact steps, and vaguely recall there was something about 32bit vs 64bit setup etc - but am wondering if things have advanced a bit and whether its much simpler these days? Iâve seen references to Docker images for Pharo, and am wondering if now that is a prime time way to easily get a small demo application up and running with minimal fuss. >>> >>> Does anyone have advice - or something to point me to? >>> >>> Ideally I want to hook something up in Gitlab CI do deploy to this thing automatically (this is where I got to a few years ago - but in picking things back up I am hoping this has all got much simpler). >>> >>> Tim

April 6, 2021

Re: Help Needed: Looking for projects to use in a study of transforming deprecations

by Gabriel Cotelli

We have several projects in the Buenos Aires Smalltalk group that can match (we provide in fact a migration package when breaking backward compatibility including transformation rules so you have a human benchmark to compare). Here the ones with more history and releases: - https://github.com/ba-st/Willow - https://github.com/ba-st/Superluminal - https://github.com/ba-st/Stargate - https://github.com/ba-st/Boardwalk - https://github.com/ba-st/Hyperspace - https://github.com/ba-st/Buoy Releases with changes in the major version are the ones breaking backward compatibility. And if you want to test something with a massive amount of code try https://github.com/ba-st/HighchartsSt. It usually breaks all the tools given the size of the codebase. Gabriel On Tue, Apr 6, 2021 at 9:50 AM Oleksandr Zaitsev <olk.zaytsev(a)gmail.com> wrote: > Hello, > > I need your help to recommend some projects that I can use in my study of > transforming deprecations. > > As many of you know, Pharo supports a very powerful concept of > "transforming" deprecations. You can deprecate a method, providing a > transformation rule. Then when a client application calls the deprecated > method, the call-site will be automatically rewritten to use the new API. > Here is an example of a transforming deprecation: > > Collection >> includesAllOf: values > self > deprecated: âUse #includesAll: insteadâ > transformWith: â`@rec includesAllOf: `@argâ -> > â`@rec includesAll: `@argâ. > > ^ self includesAll: values > > > You can read more about transforming deprecations in my blog post: > https://blog.oleks.fr/deprewriter > > I am working on a tool that can analyse the commit history of a project > and recommend deprecations and transformation rules that can be inserted > before the release. It works like this: > > 1. Collect all commits between two releases of a project > 2. Mine those commits to identify method call replacements (deletions and > additions) that happen frequently > 3. Infer the mapping between the methods of the old and new API > 4. Recommend deprecations and generate transformation rules > > I have validated my approach on Pharo, Moose, Pillar, Famix, and DataFrame > projects. > > Now I am looking for other projects that could benefit from recommended > deprecations and could be used in my study. > > *Required:* > - open source project with accessible commit history (e.g. public git > repository) > - written in Pharo (although if you know projects in other languages that > could be interesting for my study, please let me know about them as well) > > *Prefered:* > - ongoing development > - multiple releases > - has users (other projects that depend on it) > > If you have some projects in mind, please let me know about them! > > And if you are interested in this study and want to learn more, don't > hesitate to contact me by email. > > Oleksandr > > >

April 6, 2021

Re: Help Needed: Looking for projects to use in a study of transforming deprecations

by serge.stinckwich＠gmail.com

I guess CORMAS project could benefit on that. We have tons of methods we donât know if they are still used, some are deprecated or not. A real mess ð Sent from my iPhone > On 6 Apr 2021, at 20:50, Oleksandr Zaitsev <olk.zaytsev(a)gmail.com> wrote: > > ï»¿ > Hello, > > I need your help to recommend some projects that I can use in my study of transforming deprecations. > > As many of you know, Pharo supports a very powerful concept of "transforming" deprecations. You can deprecate a method, providing a transformation rule. Then when a client application calls the deprecated method, the call-site will be automatically rewritten to use the new API. Here is an example of a transforming deprecation: > > Collection >> includesAllOf: values > self > deprecated: âUse #includesAll: insteadâ > transformWith: â`@rec includesAllOf: `@argâ -> > â`@rec includesAll: `@argâ. > > ^ self includesAll: values > > You can read more about transforming deprecations in my blog post: https://blog.oleks.fr/deprewriter > > I am working on a tool that can analyse the commit history of a project and recommend deprecations and transformation rules that can be inserted before the release. It works like this: > > 1. Collect all commits between two releases of a project > 2. Mine those commits to identify method call replacements (deletions and additions) that happen frequently > 3. Infer the mapping between the methods of the old and new API > 4. Recommend deprecations and generate transformation rules > > I have validated my approach on Pharo, Moose, Pillar, Famix, and DataFrame projects. > > Now I am looking for other projects that could benefit from recommended deprecations and could be used in my study. > > Required: > - open source project with accessible commit history (e.g. public git repository) > - written in Pharo (although if you know projects in other languages that could be interesting for my study, please let me know about them as well) > > Prefered: > - ongoing development > - multiple releases > - has users (other projects that depend on it) > > If you have some projects in mind, please let me know about them! > > And if you are interested in this study and want to learn more, don't hesitate to contact me by email. > > Oleksandr > >

April 6, 2021

Help Needed: Looking for projects to use in a study of transforming deprecations

by Oleksandr Zaitsev

Hello, I need your help to recommend some projects that I can use in my study of transforming deprecations. As many of you know, Pharo supports a very powerful concept of "transforming" deprecations. You can deprecate a method, providing a transformation rule. Then when a client application calls the deprecated method, the call-site will be automatically rewritten to use the new API. Here is an example of a transforming deprecation: Collection >> includesAllOf: values self deprecated: âUse #includesAll: insteadâ transformWith: â`@rec includesAllOf: `@argâ -> â`@rec includesAll: `@argâ. ^ self includesAll: values You can read more about transforming deprecations in my blog post: https://blog.oleks.fr/deprewriter I am working on a tool that can analyse the commit history of a project and recommend deprecations and transformation rules that can be inserted before the release. It works like this: 1. Collect all commits between two releases of a project 2. Mine those commits to identify method call replacements (deletions and additions) that happen frequently 3. Infer the mapping between the methods of the old and new API 4. Recommend deprecations and generate transformation rules I have validated my approach on Pharo, Moose, Pillar, Famix, and DataFrame projects. Now I am looking for other projects that could benefit from recommended deprecations and could be used in my study. *Required:* - open source project with accessible commit history (e.g. public git repository) - written in Pharo (although if you know projects in other languages that could be interesting for my study, please let me know about them as well) *Prefered:* - ongoing development - multiple releases - has users (other projects that depend on it) If you have some projects in mind, please let me know about them! And if you are interested in this study and want to learn more, don't hesitate to contact me by email. Oleksandr

April 6, 2021

Re: Recommended way to move a package

by Sean P. DeNigris

Long Haired David wrote > File out a package on one and file it in on the other This is the lowest level approach. Except for the simplest cases, you're probably better off using Metacello. Long Haired David wrote > I can get the basic package in but the extensions never appear Are the classes to be extended loaded in the image beforehand? There was an old bug I reported [1] where extension methods were not included in a package fileout, but I don't recall it ever being fixed. If you look at the fileout file in a text editor, are the methods there? Again, I would just use Metacello... ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

April 5, 2021

Recommended way to move a package

by David Pennington

I have Pharo 8.0 on my MacBookAir and Pharo 9.0 on my server. I have having lost of trouble doing what I thought would be a simple process - File out a package on one and file it in on the other but I having lo=ts of trouble - to many issues to document to be honest. So, tell me, how do I do this so that my package is in the new image along with the code extensions to other classes listed as being in the package. I can get the basic package in but the extensions never appear and I have too many to import individually. Help! David

April 3, 2021

Re: Whats the easiest/cheapest way to run a Pharo web app in 2021?

by StÃ©phane Ducasse

esteban I would like to have a success story for the Pharo web site Could you come up with two paragraphs? And if you have a visual it would be perfect. Remember a success story is that you could do something not that your app become facebook. S. > On 2 Apr 2021, at 16:32, Esteban Maringolo <emaringolo(a)gmail.com> wrote: > > I've been running a Pharo application since August last year, > initially setup with everything inside a Docker swarm (database, > reverse proxy and Pharo workers for the UI and REST API). > > I wanted to give Docker a try because I thought it was going to be > "better". After having some issues with the Swarm networking affecting > PostgreSQL connections [1], I ended up having a hybrid that is not the > best of both worlds (I wouldn't say it's the worst either). > > So my summary is that unless you have several host machines, having a > "swarm" is completely overkill and brings more friction than anything > else. > The plus of docker is that from Gitlab everytime I push a commit to > master, a new docker image is created and I can update things smoothly > on the server by pulling the image and upgrading the stack service. > > "Whenever I have time" I plan to make the reverse proxy external to > docker (I currently use traefik as a container), and just keep the > database and Pharo workers as docker containers. > > As for the stability, I only shut it down for upgrades, but in > February I tried with a single VM+image serving everything (just to > measure real use) and albeit it was a little slower, it handled > everything perfectly [2] without a single hiccup. > > > Regards, > > [1] https://twitter.com/emaringolo/status/1296635983358763010 > [2] https://twitter.com/emaringolo/status/1360247046553362432 > > Esteban A. Maringolo > > > On Fri, Apr 2, 2021 at 6:33 AM Tim Mackinnon <tim(a)testit.works> wrote: >> >> Thanks Sanjay - you have reminded me that I have some similar notes somewhere (now located) that did the command line foo to get things running - looking at mine there was quite a big of dance to provide a way to gracefully stop and start the image so that you can easily and automatically redeploy your changes (read: use Github actions or Gitlab CI). >> >> So Iâm curious on whether Docker is now sufficiently stable stable/easy/cheap to make it a viable alternative - and whether that is also cost efficient. >> >> Pablo wrote a recent blog post on running Pharo in Docker using the BA images - https://thepharo.dev/2021/02/24/running-pharo-9-in-docker/ - but while easy on the surface, if anything goes wrong - there seems to be very little debug output to know what has happened (Iâll post separately on this - as Iâm looking at comparing options here). >> >> With Docker options, I notice that dockerize.io (not used, just a quick search) - has a micro plan for $2/m - but is 500mb ram enough (there is a $5 one for 1gm ram). >> >> Or - I stick with DigitalOcean and roll my own like before - and perhaps that has got a bit simpler. >> >> Iâm still curious what the wider community is doing. >> >> >> Tim >> >> On 2 Apr 2021, at 05:43, Sanjay Minni <sm(a)planage.com> wrote: >> >> Hi Tim >> >> Here are my notes on installing Pharo in a DigitalOcean Ubuntu droplet. >> I usually go thru a Windows Command prompt box having installed xfec4 in the ubuntu droplet, but the command line connect and graphical remote may be easier for a Linux users. my ssh public key is also in the DO droplet >> Now the first step for me is a installing Pharo launcher thru command line and then everything is thru graphical interface >> >> Installing and checking Pharo-Launcher, Installing Pharo 8 64 bit from pharo.org (instructions as on Pharo.org) >> 1. In Windows 10 command prompt connect thru > ssh root@<Droplet-ip> >> 2. cd >> 3. curl -o pharo-launcher.zip -L https://files.pharo.org/pharo-launcher/linux64 >> 4. unzip pharo-launcher.zip >> or thru the GUI-> extract here >> (pharo-launcher files will be extracted in ./pharo-launcher) >> Now while connected to the linux graphical interface thru windows remote terminal and in the GUI >> 5. Create a icon on desktop thru right-click âCreate Launcherâ for pharo-launcher >> 6. Create pharo images thru pharo-launcher >> >> hope this is of use >> >> Sanjay Minni >> >> On Thu, 1 Apr 2021 at 16:31, Tim Mackinnon <tim(a)testit.works> wrote: >>> >>> Hi everyone - its been a few year since I last hosted a little Pharo web app - and the last time I did, Sven pointed me to DigitalOcean and creating a tiny instance and configuring an Ubuntu server and then copying a pharo image on to that. It recall it wasnât too bad, albeit a bit fiddlyâ¦ >>> >>> Now several years later - I canât recall the exact steps, and vaguely recall there was something about 32bit vs 64bit setup etc - but am wondering if things have advanced a bit and whether its much simpler these days? Iâve seen references to Docker images for Pharo, and am wondering if now that is a prime time way to easily get a small demo application up and running with minimal fuss. >>> >>> Does anyone have advice - or something to point me to? >>> >>> Ideally I want to hook something up in Gitlab CI do deploy to this thing automatically (this is where I got to a few years ago - but in picking things back up I am hoping this has all got much simpler). >>> >>> Tim >> >> -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Aurore Dalle FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

April 3, 2021

Re: Problem installing Seaside on Windows

by Sven Van Caekenberghe

I normally build on the server where I deploy (linux of course), but you do not have to. Pharo is cross platform. So it is perfectly possible to build your deployment image on your mac, copy it over and run it on the server. I would always advise to not save the image with running servers inside, but to use a start up script to start your server explicitly. > On 2 Apr 2021, at 19:32, David Pennington <david(a)totallyobjects.com> wrote: > > Thank you to everyone for your help. I sorted out the public and private keys and shortened the path but it kept up with an authentication issue. I deleted everything and installed V 9.0. I shortened its name and ran the GitHub code and I now have Seaside installed and running. I now need to install STON and I can get my code working. > > What a great community this is! > > David > > > > On 02/04/2021 17:43, TomaÅ¾ Turk wrote: > >> According to my experiences this happens if Pharo images are located deeply in the directory path. It helps if you move the image in question to some higher level. In any case, C:\Pharo should work no matter what. >> >> Seaside has lots of dependencies which are then located under its repository. >> >> Tomaz >> >> On Fri, 2 Apr 2021, 18:31 Sanjay Minni, <sm(a)planage.com> wrote: >> Yes you hit the window filename length problem. >> >> Retry by creating one more pharo 8 image. Only don't take the default image name as you have taken. Change it to very short like p8-1 to keep image file name and consequently the folder name length to a minimum >> >> Then install seaside. >> >> If that doesn't work repost and we will try still another option >> >> Regards >> Sanjay >> >> On Fri, 2 Apr, 2021, 9:36 pm David Pennington, <david(a)totallyobjects.com> wrote: >> OK, I got my software working fine on the Mac but I really need it on Windows now so I have had another go. I have followed all the instructions and I have a public key registered with GIT for both the Mac and the Windows laptop. The Mac now quite happily installs stuff that wouldn't load before. (TinyLogger). However, the Windows laptop now get a lot further with the Seaside install but fails with this message: >> >> "LGit_GIT_EEXISTS: Failed to stat file 'C:/Users/david/Documents/Pharo/images/Pharo 8.0 - 64bit (sta...aximumAbsoluteAge.maximumRelativeAge.overflowAction..st': The filename or extension is too long. >> " >> Any thoughts? >> >> >> On 22/03/2021 18:18, David Pennington wrote: >> >> I am sorry but github is a mystery to me. I installed all of this on my mac with no troubles. Surely it can't be anymore difficult on PC? >> >> On 22 Mar 2021 18:05, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> david >> >> did you succeed to clone or checkout a github repo from this machine and without pharo at all? >> Because Pharo is just using libgit. >> >> S. >> >> On 22 Mar 2021, at 18:58, David Pennington <david(a)totallyobjects.com> wrote: >> >> Tried that. I got the following >> >> Failed to get server certificate: the handle is in the wrong state for the requested operation. >> >> I assume that someone thinks that this is helpful:-) >> >> On 22 Mar 2021 16:06, Sanjay Minni <sm(a)planage.com> wrote: >> Hi David, >> >> I have repeatedly installed Seaside on Pharo 8 / 9 64 bit - Windows 10 >> without any issues and I have done it both ssh and https >> >> I do it quickly / simply by >> >> tools->iceberg->[+ add] (on top panel right) >> on popup select: 'clone from github.com' >> fill in owner: SeasideSt (case does not matter) >> project: seaside >> local directory: (leave the default for >> now) >> protocol try https first (not >> sure if github requires a password) >> or ssh which may be >> slightly complicated >> once seaside libraries are pulled in and seaside appears in the iceberg >> panel then >> right click on seaside >> on popup scroll down to metacello->install baseline (default) >> >> hope that works >> >> >> >> >> Long Haired David wrote >> > Hi everyone. >> > >> > I have been developing a new web site using Seaside on my M1 MacBookAir >> > and I have had no issues. >> > >> > To deploy it, I have to install Pharo on either a Windows 10 or a Windows >> > Server 2012 server. Pharo has installed on both without any issues. >> > However, I am having problems installing Seaside. >> > >> > I have Pharo 8.0 installed on both (64 bit version). >> > >> > If I try and install from the Catalog, I get the following error in the >> > Transcript. >> > >> > IceGenericError: Failed to stat file >> > 'C:/Users/david/Documents/Pharo/images/Pharo 8.0 - 64bit >> > (stable)/pharo-local. >> > >> > If I try using Monticello, I get the following: >> > >> > Metacello new >> > baseline:'Seaside3'; >> > repository: 'github://SeasideSt/Seaside:master/repository'; >> > load >> > I got an error while cloning: There was an authentication error while >> > trying to execute the operation: . >> > This happens usually because you didn't provide a valid set of >> > credentials. >> > You may fix this problem in different ways: >> > >> > 1. adding your keys to ssh-agent, executing ssh-add ~/.ssh/id_rsa in your >> > command line. >> > 2. adding your keys in settings (open settings browser search for "Use >> > custom SSH keys" and >> > add your public and private keys). >> > 3. using HTTPS instead SSH (Just use an url in the form HTTPS://etc.git) >> > I will try to clone the HTTPS variant. >> > >> > Can you help please? >> > >> > David >> > Totally Objects >> >> >> >> >> >> ----- >> cheers, >> Sanjay >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> >> >> -------------------------------------------- >> StÃ©phane Ducasse >> http://stephane.ducasse.free.fr / http://www.pharo.org >> 03 59 35 87 52 >> Assistant: Aurore Dalle >> FAX 03 59 57 78 50 >> TEL 03 59 35 86 16 >> S. Ducasse - Inria >> 40, avenue Halley, >> Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza >> Villeneuve d'Ascq 59650 >> France

April 2, 2021

Re: Problem installing Seaside on Windows

by David Pennington

Thank you to everyone for your help. I sorted out the public and private keys and shortened the path but it kept up with an authentication issue. I deleted everything and installed V 9.0. I shortened its name and ran the GitHub code and I now have Seaside installed and running. I now need to install STON and I can get my code working. What a great community this is! David On 02/04/2021 17:43, TomaÅ¾ Turk wrote: > According to my experiences this happens if Pharo images are located deeply in the directory path. It helps if you move the image in question to some higher level. In any case, C:\Pharo should work no matter what. > > Seaside has lots of dependencies which are then located under its repository. > > Tomaz > > On Fri, 2 Apr 2021, 18:31 Sanjay Minni, <sm(a)planage.com> wrote: > Yes you hit the window filename length problem. > > Retry by creating one more pharo 8 image. Only don't take the default image name as you have taken. Change it to very short like p8-1 to keep image file name and consequently the folder name length to a minimum > > Then install seaside. > > If that doesn't work repost and we will try still another option > > Regards > Sanjay > > On Fri, 2 Apr, 2021, 9:36 pm David Pennington, <david(a)totallyobjects.com> wrote: > > OK, I got my software working fine on the Mac but I really need it on Windows now so I have had another go. I have followed all the instructions and I have a public key registered with GIT for both the Mac and the Windows laptop. The Mac now quite happily installs stuff that wouldn't load before. (TinyLogger). However, the Windows laptop now get a lot further with the Seaside install but fails with this message: > > "LGit_GIT_EEXISTS: Failed to stat file 'C:/Users/david/Documents/Pharo/images/Pharo 8.0 - 64bit (sta...aximumAbsoluteAge.maximumRelativeAge.overflowAction..st': The filename or extension is too long. > " > Any thoughts? > > On 22/03/2021 18:18, David Pennington wrote: > > I am sorry but github is a mystery to me. I installed all of this on my mac with no troubles. Surely it can't be anymore difficult on PC? > > On 22 Mar 2021 18:05, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > david > > did you succeed to clone or checkout a github repo from this machine and without pharo at all? > Because Pharo is just using libgit. > > S. > > On 22 Mar 2021, at 18:58, David Pennington <david(a)totallyobjects.com> wrote: > > Tried that. I got the following > > Failed to get server certificate: the handle is in the wrong state for the requested operation. > > I assume that someone thinks that this is helpful:-) > > On 22 Mar 2021 16:06, Sanjay Minni <sm(a)planage.com> wrote: > > Hi David, > > I have repeatedly installed Seaside on Pharo 8 / 9 64 bit - Windows 10 > without any issues and I have done it both ssh and https > > I do it quickly / simply by > > tools->iceberg->[+ add] (on top panel right) > on popup select: 'clone from github.com [1]' > fill in owner: SeasideSt (case does not matter) > project: seaside > local directory: (leave the default for > now) > protocol try https first (not > sure if github requires a password) > or ssh which may be > slightly complicated > once seaside libraries are pulled in and seaside appears in the iceberg > panel then > right click on seaside > on popup scroll down to metacello->install baseline (default) > > hope that works > > Long Haired David wrote >> Hi everyone. >> >> I have been developing a new web site using Seaside on my M1 MacBookAir >> and I have had no issues. >> >> To deploy it, I have to install Pharo on either a Windows 10 or a Windows >> Server 2012 server. Pharo has installed on both without any issues. >> However, I am having problems installing Seaside. >> >> I have Pharo 8.0 installed on both (64 bit version). >> >> If I try and install from the Catalog, I get the following error in the >> Transcript. >> >> IceGenericError: Failed to stat file >> 'C:/Users/david/Documents/Pharo/images/Pharo 8.0 - 64bit >> (stable)/pharo-local. >> >> If I try using Monticello, I get the following: >> >> Metacello new >> baseline:'Seaside3'; >> repository: 'github://SeasideSt/Seaside:master/repository'; >> load >> I got an error while cloning: There was an authentication error while >> trying to execute the operation: . >> This happens usually because you didn't provide a valid set of >> credentials. >> You may fix this problem in different ways: >> >> 1. adding your keys to ssh-agent, executing ssh-add ~/.ssh/id_rsa in your >> command line. >> 2. adding your keys in settings (open settings browser search for "Use >> custom SSH keys" and >> add your public and private keys). >> 3. using HTTPS instead SSH (Just use an url in the form HTTPS://etc.git) >> I will try to clone the HTTPS variant. >> >> Can you help please? >> >> David >> Totally Objects > > ----- > cheers, > Sanjay > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Aurore Dalle FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France Links: ------ [1] http://github.com

April 2, 2021

Re: Problem installing Seaside on Windows

by TomaÅ¾ Turk

According to my experiences this happens if Pharo images are located deeply in the directory path. It helps if you move the image in question to some higher level. In any case, C:\Pharo should work no matter what. Seaside has lots of dependencies which are then located under its repository. Tomaz On Fri, 2 Apr 2021, 18:31 Sanjay Minni, <sm(a)planage.com> wrote: > Yes you hit the window filename length problem. > > Retry by creating one more pharo 8 image. Only don't take the default > image name as you have taken. Change it to very short like p8-1 to keep > image file name and consequently the folder name length to a minimum > > Then install seaside. > > If that doesn't work repost and we will try still another option > > Regards > Sanjay > > On Fri, 2 Apr, 2021, 9:36 pm David Pennington, <david(a)totallyobjects.com> > wrote: > >> OK, I got my software working fine on the Mac but I really need it on Windows now so I have had another go. I have followed all the instructions and I have a public key registered with GIT for both the Mac and the Windows laptop. The Mac now quite happily installs stuff that wouldn't load before. (TinyLogger). However, the Windows laptop now get a lot further with the Seaside install but fails with this message: >> >> >> "LGit_GIT_EEXISTS: Failed to stat file >> 'C:/Users/david/Documents/Pharo/images/Pharo 8.0 - 64bit >> (sta...aximumAbsoluteAge.maximumRelativeAge.overflowAction..st': The >> filename or extension is too long. >> " >> Any thoughts? >> >> >> On 22/03/2021 18:18, David Pennington wrote: >> >> I am sorry but github is a mystery to me. I installed all of this on my >> mac with no troubles. Surely it can't be anymore difficult on PC? >> >> On 22 Mar 2021 18:05, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> >> david >> >> did you succeed to clone or checkout a github repo from this machine and >> without pharo at all? >> Because Pharo is just using libgit. >> >> S. >> >> On 22 Mar 2021, at 18:58, David Pennington <david(a)totallyobjects.com> >> wrote: >> >> Tried that. I got the following >> >> Failed to get server certificate: the handle is in the wrong state for >> the requested operation. >> >> I assume that someone thinks that this is helpful:-) >> >> On 22 Mar 2021 16:06, Sanjay Minni <sm(a)planage.com> wrote: >> >> Hi David, >> >> I have repeatedly installed Seaside on Pharo 8 / 9 64 bit - Windows 10 >> without any issues and I have done it both ssh and https >> >> I do it quickly / simply by >> >> tools->iceberg->[+ add] (on top panel right) >> on popup select: 'clone from github.com' >> fill in owner: SeasideSt (case does not >> matter) >> project: seaside >> local directory: (leave the default for >> now) >> protocol try https first (not >> sure if github requires a password) >> or ssh which may >> be >> slightly complicated >> once seaside libraries are pulled in and seaside appears in the iceberg >> panel then >> right click on seaside >> on popup scroll down to metacello->install baseline (default) >> >> hope that works >> >> >> >> >> Long Haired David wrote >> > Hi everyone. >> > >> > I have been developing a new web site using Seaside on my M1 MacBookAir >> > and I have had no issues. >> > >> > To deploy it, I have to install Pharo on either a Windows 10 or a >> Windows >> > Server 2012 server. Pharo has installed on both without any issues. >> > However, I am having problems installing Seaside. >> > >> > I have Pharo 8.0 installed on both (64 bit version). >> > >> > If I try and install from the Catalog, I get the following error in the >> > Transcript. >> > >> > IceGenericError: Failed to stat file >> > 'C:/Users/david/Documents/Pharo/images/Pharo 8.0 - 64bit >> > (stable)/pharo-local. >> > >> > If I try using Monticello, I get the following: >> > >> > Metacello new >> > baseline:'Seaside3'; >> > repository: 'github://SeasideSt/Seaside:master/repository'; >> > load >> > I got an error while cloning: There was an authentication error while >> > trying to execute the operation: . >> > This happens usually because you didn't provide a valid set of >> > credentials. >> > You may fix this problem in different ways: >> > >> > 1. adding your keys to ssh-agent, executing ssh-add ~/.ssh/id_rsa in >> your >> > command line. >> > 2. adding your keys in settings (open settings browser search for "Use >> > custom SSH keys" and >> > add your public and private keys). >> > 3. using HTTPS instead SSH (Just use an url in the form HTTPS://etc.git) >> >> > I will try to clone the HTTPS variant. >> > >> > Can you help please? >> > >> > David >> > Totally Objects >> >> >> >> >> >> ----- >> cheers, >> Sanjay >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> >> >> -------------------------------------------- >> StÃ©phane Ducasse >> http://stephane.ducasse.free.fr / http://www.pharo.org >> 03 59 35 87 52 >> Assistant: Aurore Dalle >> FAX 03 59 57 78 50 >> TEL 03 59 35 86 16 >> S. Ducasse - Inria >> 40, avenue Halley, >> Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza >> Villeneuve d'Ascq 59650 >> France >> >>

April 2, 2021