Smalltalk › Gemtalk › GLASS

Upgrade Grease behind firewall

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

10 messages Options

BrunoBB

Upgrade Grease behind firewall

Hi all,

I want to run a installation script and the first step is:
Gofer new
package: 'GsUpgrader-Core';
url: 'http://ss3.gemtalksystems.com/ss/gsUpgrader';
load.
(Smalltalk at: #GsUpgrader) upgradeGrease.

But i having an error, i think a Socket can no connect to repository port.
This installation is behind a lot of firewalls.
The socket is 'ss3.gemtalksystems.com' port 80 (aHTTPSocket).
The strange this is that:
curl 204.246.122.142:80
This is reposnding a 404 by is reachable...

Any idea what could be blocking the connection ?

Regards,
Bruno
The error is:
GoferRepositoryError (AbstractException) >> _signalWith: @6 line 25
GoferRepositoryError (AbstractException) >> signal: @3 line 7
GoferRepositoryError class >> signal:repository: @4 line 2
[] in ExecBlock1 (MCFileBasedRepository) >> goferReferences @4 line 5
SpSocketError (AbstractException) >> _executeHandler: @4 line 8
SpSocketError (AbstractException) >> _signalWith: @1 line 1
SpSocketError (AbstractException) >> signal: @3 line 7
SpSocketError class (AbstractException class) >> signal: @3 line 4
SpSocketError class (SpAbstractError class) >> raiseSignal: @2 line 2
HTTPSocket (SpSocket) >> connectTo: @10 line 7
HTTPSocket class (SpSocket class) >> connectToServerOnHost:port: @6 line 7
HTTPSocket class >> httpGetDocument:args:accept:request: @62 line 38
HTTPSocket class >> httpGet:args:accept:request: @3 line 6
HTTPSocket class >> httpGet:args:user:passwd: @12 line 5
MCPlatformSupport class >> readStreamForUrl:user:passwd:do: @3 line 3
MCHttpRepository >> allFileNames @7 line 3
MCHttpRepository (MCFileBasedRepository) >> readableFileNames @3 line 2
MCHttpRepository (MCFileBasedRepository) >> allVersionNames @3 line 2
[] in ExecBlock0 (MCFileBasedRepository) >> goferReferences @3 line 3
ExecBlock0 (ExecBlock) >> on:do: @3 line 44
MCHttpRepository (MCFileBasedRepository) >> goferReferences @3 line 4
[] in ExecBlock0 (Gofer) >> basicReferencesIn: @3 line 2
ExecBlock0 (ExecBlock) >> on:do: @3 line 44
Gofer >> basicReferencesIn: @3 line 3
[] in ExecBlock0 (Gofer) >> allResolvedIn: @3 line 5
Dictionary (AbstractDictionary) >> at:ifAbsentPut: @8 line 14
Gofer >> allResolvedIn: @6 line 5
[] in ExecBlock1 (Gofer) >> allResolved @3 line 7
Array (Collection) >> do: @6 line 10
Gofer >> allResolved @6 line 7
GoferPackageReference (GoferReference) >> resolveAllWith: @3 line 4
GoferPackageReference (GoferReference) >> resolveWith: @3 line 5
[] in ExecBlock1 (Gofer) >> resolved @3 line 4
Array (SequenceableCollection) >> collect: @10 line 16
Gofer >> resolved @4 line 4
GoferLoad >> initializeOn: @4 line 3
GoferLoad class (GoferOperation class) >> on: @3 line 2
Gofer >> execute:do: @4 line 3
Gofer >> execute: @2 line 2
Gofer >> load @2 line 4
Executed Code @5 line 4
GsNMethod class >> _gsReturnToC @1 line 1

BrunoBB

Re: Upgrade Grease behind firewall

Hi,

Sorry for so many mails...

we have sort out the problem with (is working now):
Gofer new
package: 'GsUpgrader-Core';
url: 'http://ss3.gemtalksystems.com/ss/gsUpgrader';
load.
(Smalltalk at: #GsUpgrader) upgradeGrease.

Now the problem is with:
GsDeployer deploy: [
Metacello new
baseline: 'Seaside3';
repository: 'github://GsDevKit/Seaside31:gs_master/repository';
onLock: [:ex | ex honor];
load: 'CI' ].

Trying to install Seaside generate the following error:
UserDefinedError (AbstractException) >> _signalWith: @6 line 25
UserDefinedError (AbstractException) >> signal @2 line 47
MetacelloGemStonePlatform (Object) >> error: @6 line 7
[] in ExecBlock2 (MetacelloGemStonePlatform) >> downloadJSON:eTagsCache:eTagsKey:username:pass: @13 line 39
[] in ExecBlock1 (MetacelloGemStonePlatform) >> downloadJSON:eTagsCache:eTagsKey:username:pass: @3 line 90
LookupError (AbstractException) >> _executeHandler: @4 line 8
LookupError (AbstractException) >> _signalWith: @1 line 1
LookupError (AbstractException) >> signal @2 line 47
Dictionary (Object) >> _error:args: @16 line 11
Dictionary (AbstractDictionary) >> _errorKeyNotFound: @2 line 5
Dictionary >> at: @6 line 8
[] in ExecBlock2 (MetacelloGemStonePlatform) >> downloadJSON:eTagsCache:eTagsKey:username:pass: @3 line 53
MetacelloGemStonePlatform >> extractHTTPHeader:do: @34 line 26
[] in ExecBlock0 (MetacelloGemStonePlatform) >> downloadJSON:eTagsCache:eTagsKey:username:pass: @9 line 50
ExecBlock0 (ExecBlock) >> on:do: @3 line 44
[] in ExecBlock1 (MetacelloGemStonePlatform) >> downloadJSON:eTagsCache:eTagsKey:username:pass: @3 line 89
[] in ExecBlock0 (FileDirectory) >> readOnlyFileNamed:do: @3 line 4
ExecBlock0 (ExecBlock) >> ensure: @2 line 12
ServerFileDirectory (FileDirectory) >> readOnlyFileNamed:do: @5 line 4
MetacelloGemStonePlatform >> downloadJSON:eTagsCache:eTagsKey:username:pass: @18 line 43
MCGitHubRepository >> downloadJSONTags @14 line 5
MCGitHubRepository (MCGitBasedNetworkRepository) >> resolveProjectVersionPattern: @10 line 8
MCGitHubRepository (MCGitBasedNetworkRepository) >> projectVersion: @11 line 15
MCGitHubRepository (MCGitBasedNetworkRepository) >> projectPath:projectVersion:repoPath: @3 line 3
MCGitHubRepository class (MCGitBasedNetworkRepository class) >> parseLocation:version: @48 line 36
MCGitHubRepository class (MCGitBasedNetworkRepository class) >> location:version: @2 line 2
MCGitHubRepository class (MCGitBasedNetworkRepository class) >> location: @2 line 2
[] in ExecBlock1 (MetacelloPlatform) >> createRepository: @6 line 31
SmalltalkProxy >> at:ifPresent: @11 line 7
MetacelloGemStonePlatform (MetacelloPlatform) >> createRepository: @20 line 28
MetacelloGemStonePlatform >> createRepository: @54 line 45
MetacelloMCBaselineProject (MetacelloMCProject) >> createRepository: @3 line 3
MetacelloRepositorySpec >> createRepository @4 line 3
[] in ExecBlock0 (MetacelloCommonMCSpecLoader) >> repositoriesFrom:ignoreOverrides: @3 line 9
Array (SequenceableCollection) >> detect:ifNone: @12 line 10
[] in ExecBlock1 (MetacelloCommonMCSpecLoader) >> repositoriesFrom:ignoreOverrides: @5 line 9
OrderedCollection (Collection) >> do: @6 line 10
MetacelloEnsureFetchingMCSpecLoader (MetacelloCommonMCSpecLoader) >> repositoriesFrom:ignoreOverrides: @15 line 7
MetacelloEnsureFetchingMCSpecLoader (MetacelloCommonMCSpecLoader) >> repositoriesFrom: @2 line 3
MetacelloPackageSpec >> explicitLoadUsing: @24 line 15
MetacelloPackageSpec >> ensureLoadUsing: @3 line 2
MetacelloMCBaselineOfProjectSpec (MetacelloMCProjectSpec) >> ensureLoadUsing: @15 line 13
[] in ExecBlock0 (MetacelloMCBaselineOfProjectSpec) >> ensureLoadUsing: @3 line 5
ExecBlock0 (ExecBlock) >> on:do: @3 line 44
MetacelloMCBaselineOfProjectSpec >> ensureLoadUsing: @3 line 6
MetacelloMCBaselineOfProjectSpec (MetacelloMCProjectSpec) >> ensureLoadedForDevelopmentUsing: @36 line 39
[] in ExecBlock1 (MetacelloMCVersionSpecLoader) >> load @3 line 8
OrderedCollection (Collection) >> do: @6 line 10
MetacelloMCVersionSpecLoader >> load @9 line 7
MetacelloMCVersion >> executeLoadFromArray: @10 line 7
[] in ExecBlock1 (MetacelloMCVersion) >> fetchRequiredFromArray: @3 line 11
[] in ExecBlock0 (MetacelloPlatform) >> useStackCacheDuring:defaultDictionary: @3 line 9
ExecBlock0 (ExecBlock) >> on:do: @3 line 44
MetacelloGemStonePlatform (MetacelloPlatform) >> useStackCacheDuring:defaultDictionary: @10 line 10
[] in ExecBlock0 (MetacelloMCVersion) >> fetchRequiredFromArray: @7 line 11
ExecBlock0 (ExecBlock) >> ensure: @2 line 12
[] in ExecBlock0 (MetacelloMCVersion) >> fetchRequiredFromArray: @3 line 12
MetacelloGemStonePlatform (MetacelloPlatform) >> do:displaying: @2 line 3
MetacelloMCVersion >> fetchRequiredFromArray: @18 line 7
[] in ExecBlock0 (MetacelloMCVersion) >> doLoadRequiredFromArray: @4 line 10
ExecBlock0 (ExecBlock) >> ensure: @2 line 12
MetacelloMCVersion >> doLoadRequiredFromArray: @23 line 16
String >> loadRequiredForMetacelloMCVersion: @3 line 3
MetacelloMCVersion >> load: @2 line 3
[] in ExecBlock0 (MetacelloScriptEngine) >> load:onProjectDownGrade:onProjectUpgrade: @11 line 16
ExecBlock0 (ExecBlock) >> on:do: @3 line 44
[] in ExecBlock0 (MetacelloScriptEngine) >> handleNotificationsForAction: @7 line 6
ExecBlock0 (ExecBlock) >> on:do: @3 line 44
[] in ExecBlock0 (MetacelloScriptEngine) >> handleNotificationsForAction: @5 line 14
ExecBlock0 (ExecBlock) >> on:do: @3 line 44
[] in ExecBlock0 (MetacelloScriptEngine) >> handleNotificationsForAction: @3 line 20
ExecBlock0 (ExecBlock) >> on:do: @3 line 44
MetacelloScriptEngine >> handleNotificationsForAction: @3 line 24
[] in ExecBlock0 (MetacelloScriptEngine) >> load:onProjectDownGrade:onProjectUpgrade: @3 line 5
ExecBlock0 (ExecBlock) >> ensure: @2 line 12
MetacelloProjectRegistration class >> copyRegistryRestoreOnErrorWhile: @9 line 14
MetacelloScriptEngine >> load:onProjectDownGrade:onProjectUpgrade: @3 line 3
MetacelloScriptEngine >> load: @2 line 3
MetacelloScriptEngine (Object) >> perform:withArguments: @1 line 1
[] in ExecBlock1 (MetacelloScriptExecutor) >> execute: @12 line 15
[] in ExecBlock1 (MetacelloScriptApiExecutor) >> executeString:do: @6 line 6
Array (Collection) >> do: @6 line 10
MetacelloScriptApiExecutor >> executeString:do: @7 line 4
String >> execute:against: @2 line 2
MetacelloScriptApiExecutor (MetacelloScriptExecutor) >> execute: @7 line 9
Metacello >> execute:args: @9 line 5
Metacello >> load: @2 line 2
[] in Executed Code @6 line 6
[] in ExecBlock0 (GsDeployer) >> deploy: @9 line 8
ExecBlock0 (ExecBlock) >> on:do: @3 line 44
[] in ExecBlock0 (GsDeployer) >> deploy: @3 line 9
[] in ExecBlock0 (MCPlatformSupport class) >> commitOnAlmostOutOfMemoryDuring: @4 line 7
ExecBlock0 (ExecBlock) >> ensure: @2 line 12
MCPlatformSupport class >> commitOnAlmostOutOfMemoryDuring: @7 line 8
[] in ExecBlock0 (GsDeployer) >> mcPlatformSupportDo: @3 line 10
ExecBlock0 (ExecBlock) >> ensure: @2 line 12
GsDeployer >> mcPlatformSupportDo: @11 line 10
GsDeployer >> deploy: @3 line 3
GsDeployer class >> autoMigrate: @3 line 12
GsDeployer class >> deploy: @2 line 12
Executed Code @2 line 1
GsNMethod class >> _gsReturnToC @1 line 1

GLASS mailing list

Re: Upgrade Grease behind firewall

I thought that you had already done a $GS_HOME/bin/createStone? ... I
guess not.

The difference between http://ss3.gemtalksystems.com/ss/gsUpgrader and
github://GsDevKit/Seaside31:gs_master/repository is that you are going
to be using https (via curl) ... What is the exact error message?

What did you have to do to make the http: stuff work?

Presumably you need to work some magic to poke holes in the firewall for
ssh ... if you need to use proxies, there are ways to use proxies from
within GsDevKit...

As an alternative, you should be able to load Seaside3 from a git
repository (clone outside your firewall and scp/rsynch inside your
firewall and then lock the repository) and pretty much avoid ssh access
altogether... if you've got tODE installed, there are fewer
manual/moving parts to make this work, but I don't know what you are
actually attempting to do, so I can't give too much detailed advice at
this point in time ...

Dale

On 06/27/2016 10:46 AM, BrunoBB via Glass wrote:

> Hi,
>
> Sorry for so many mails...
>
> we have sort out the problem with (is working now):
> Gofer new
> package: 'GsUpgrader-Core';
> url: 'http://ss3.gemtalksystems.com/ss/gsUpgrader';
> load.
> (Smalltalk at: #GsUpgrader) upgradeGrease.
>
> Now the problem is with:
> GsDeployer deploy: [
> Metacello new
> baseline: 'Seaside3';
> repository: 'github://GsDevKit/Seaside31:gs_master/repository';
> onLock: [:ex | ex honor];
> load: 'CI' ].
>
> Trying to install Seaside generate the following error:
> UserDefinedError (AbstractException) >> _signalWith: @6 line 25
> UserDefinedError (AbstractException) >> signal @2 line 47
> MetacelloGemStonePlatform (Object) >> error: @6 line 7
> [] in ExecBlock2 (MetacelloGemStonePlatform) >>
> downloadJSON:eTagsCache:eTagsKey:username:pass: @13 line 39
> [] in ExecBlock1 (MetacelloGemStonePlatform) >>
> downloadJSON:eTagsCache:eTagsKey:username:pass: @3 line 90
> LookupError (AbstractException) >> _executeHandler: @4 line 8
> LookupError (AbstractException) >> _signalWith: @1 line 1
> LookupError (AbstractException) >> signal @2 line 47
> Dictionary (Object) >> _error:args: @16 line 11
> Dictionary (AbstractDictionary) >> _errorKeyNotFound: @2 line 5
> Dictionary >> at: @6 line 8
> [] in ExecBlock2 (MetacelloGemStonePlatform) >>
> downloadJSON:eTagsCache:eTagsKey:username:pass: @3 line 53
> MetacelloGemStonePlatform >> extractHTTPHeader:do: @34 line 26
> [] in ExecBlock0 (MetacelloGemStonePlatform) >>
> downloadJSON:eTagsCache:eTagsKey:username:pass: @9 line 50
> ExecBlock0 (ExecBlock) >> on:do: @3 line 44
> [] in ExecBlock1 (MetacelloGemStonePlatform) >>
> downloadJSON:eTagsCache:eTagsKey:username:pass: @3 line 89
> [] in ExecBlock0 (FileDirectory) >> readOnlyFileNamed:do: @3 line 4
> ExecBlock0 (ExecBlock) >> ensure: @2 line 12
> ServerFileDirectory (FileDirectory) >> readOnlyFileNamed:do: @5 line 4
> MetacelloGemStonePlatform >> downloadJSON:eTagsCache:eTagsKey:username:pass:
> @18 line 43
> MCGitHubRepository >> downloadJSONTags @14 line 5
> MCGitHubRepository (MCGitBasedNetworkRepository) >>
> resolveProjectVersionPattern: @10 line 8
> MCGitHubRepository (MCGitBasedNetworkRepository) >> projectVersion: @11 line
> 15
> MCGitHubRepository (MCGitBasedNetworkRepository) >>
> projectPath:projectVersion:repoPath: @3 line 3
> MCGitHubRepository class (MCGitBasedNetworkRepository class) >>
> parseLocation:version: @48 line 36
> MCGitHubRepository class (MCGitBasedNetworkRepository class) >>
> location:version: @2 line 2
> MCGitHubRepository class (MCGitBasedNetworkRepository class) >> location: @2
> line 2
> [] in ExecBlock1 (MetacelloPlatform) >> createRepository: @6 line 31
> SmalltalkProxy >> at:ifPresent: @11 line 7
> MetacelloGemStonePlatform (MetacelloPlatform) >> createRepository: @20 line
> 28
> MetacelloGemStonePlatform >> createRepository: @54 line 45
> MetacelloMCBaselineProject (MetacelloMCProject) >> createRepository: @3 line
> 3
> MetacelloRepositorySpec >> createRepository @4 line 3
> [] in ExecBlock0 (MetacelloCommonMCSpecLoader) >>
> repositoriesFrom:ignoreOverrides: @3 line 9
> Array (SequenceableCollection) >> detect:ifNone: @12 line 10
> [] in ExecBlock1 (MetacelloCommonMCSpecLoader) >>
> repositoriesFrom:ignoreOverrides: @5 line 9
> OrderedCollection (Collection) >> do: @6 line 10
> MetacelloEnsureFetchingMCSpecLoader (MetacelloCommonMCSpecLoader) >>
> repositoriesFrom:ignoreOverrides: @15 line 7
> MetacelloEnsureFetchingMCSpecLoader (MetacelloCommonMCSpecLoader) >>
> repositoriesFrom: @2 line 3
> MetacelloPackageSpec >> explicitLoadUsing: @24 line 15
> MetacelloPackageSpec >> ensureLoadUsing: @3 line 2
> MetacelloMCBaselineOfProjectSpec (MetacelloMCProjectSpec) >>
> ensureLoadUsing: @15 line 13
> [] in ExecBlock0 (MetacelloMCBaselineOfProjectSpec) >> ensureLoadUsing: @3
> line 5
> ExecBlock0 (ExecBlock) >> on:do: @3 line 44
> MetacelloMCBaselineOfProjectSpec >> ensureLoadUsing: @3 line 6
> MetacelloMCBaselineOfProjectSpec (MetacelloMCProjectSpec) >>
> ensureLoadedForDevelopmentUsing: @36 line 39
> [] in ExecBlock1 (MetacelloMCVersionSpecLoader) >> load @3 line 8
> OrderedCollection (Collection) >> do: @6 line 10
> MetacelloMCVersionSpecLoader >> load @9 line 7
> MetacelloMCVersion >> executeLoadFromArray: @10 line 7
> [] in ExecBlock1 (MetacelloMCVersion) >> fetchRequiredFromArray: @3 line 11
> [] in ExecBlock0 (MetacelloPlatform) >>
> useStackCacheDuring:defaultDictionary: @3 line 9
> ExecBlock0 (ExecBlock) >> on:do: @3 line 44
> MetacelloGemStonePlatform (MetacelloPlatform) >>
> useStackCacheDuring:defaultDictionary: @10 line 10
> [] in ExecBlock0 (MetacelloMCVersion) >> fetchRequiredFromArray: @7 line 11
> ExecBlock0 (ExecBlock) >> ensure: @2 line 12
> [] in ExecBlock0 (MetacelloMCVersion) >> fetchRequiredFromArray: @3 line 12
> MetacelloGemStonePlatform (MetacelloPlatform) >> do:displaying: @2 line 3
> MetacelloMCVersion >> fetchRequiredFromArray: @18 line 7
> [] in ExecBlock0 (MetacelloMCVersion) >> doLoadRequiredFromArray: @4 line
> 10
> ExecBlock0 (ExecBlock) >> ensure: @2 line 12
> MetacelloMCVersion >> doLoadRequiredFromArray: @23 line 16
> String >> loadRequiredForMetacelloMCVersion: @3 line 3
> MetacelloMCVersion >> load: @2 line 3
> [] in ExecBlock0 (MetacelloScriptEngine) >>
> load:onProjectDownGrade:onProjectUpgrade: @11 line 16
> ExecBlock0 (ExecBlock) >> on:do: @3 line 44
> [] in ExecBlock0 (MetacelloScriptEngine) >> handleNotificationsForAction:
> @7 line 6
> ExecBlock0 (ExecBlock) >> on:do: @3 line 44
> [] in ExecBlock0 (MetacelloScriptEngine) >> handleNotificationsForAction:
> @5 line 14
> ExecBlock0 (ExecBlock) >> on:do: @3 line 44
> [] in ExecBlock0 (MetacelloScriptEngine) >> handleNotificationsForAction:
> @3 line 20
> ExecBlock0 (ExecBlock) >> on:do: @3 line 44
> MetacelloScriptEngine >> handleNotificationsForAction: @3 line 24
> [] in ExecBlock0 (MetacelloScriptEngine) >>
> load:onProjectDownGrade:onProjectUpgrade: @3 line 5
> ExecBlock0 (ExecBlock) >> ensure: @2 line 12
> MetacelloProjectRegistration class >> copyRegistryRestoreOnErrorWhile: @9
> line 14
> MetacelloScriptEngine >> load:onProjectDownGrade:onProjectUpgrade: @3 line 3
> MetacelloScriptEngine >> load: @2 line 3
> MetacelloScriptEngine (Object) >> perform:withArguments: @1 line 1
> [] in ExecBlock1 (MetacelloScriptExecutor) >> execute: @12 line 15
> [] in ExecBlock1 (MetacelloScriptApiExecutor) >> executeString:do: @6 line
> 6
> Array (Collection) >> do: @6 line 10
> MetacelloScriptApiExecutor >> executeString:do: @7 line 4
> String >> execute:against: @2 line 2
> MetacelloScriptApiExecutor (MetacelloScriptExecutor) >> execute: @7 line 9
> Metacello >> execute:args: @9 line 5
> Metacello >> load: @2 line 2
> [] in Executed Code @6 line 6
> [] in ExecBlock0 (GsDeployer) >> deploy: @9 line 8
> ExecBlock0 (ExecBlock) >> on:do: @3 line 44
> [] in ExecBlock0 (GsDeployer) >> deploy: @3 line 9
> [] in ExecBlock0 (MCPlatformSupport class) >>
> commitOnAlmostOutOfMemoryDuring: @4 line 7
> ExecBlock0 (ExecBlock) >> ensure: @2 line 12
> MCPlatformSupport class >> commitOnAlmostOutOfMemoryDuring: @7 line 8
> [] in ExecBlock0 (GsDeployer) >> mcPlatformSupportDo: @3 line 10
> ExecBlock0 (ExecBlock) >> ensure: @2 line 12
> GsDeployer >> mcPlatformSupportDo: @11 line 10
> GsDeployer >> deploy: @3 line 3
> GsDeployer class >> autoMigrate: @3 line 12
> GsDeployer class >> deploy: @2 line 12
> Executed Code @2 line 1
> GsNMethod class >> _gsReturnToC @1 line 1
>
>
>
>
> --
> View this message in context: http://forum.world.st/Upgrade-Grease-behind-firewall-tp4903625p4903688.html
> Sent from the GLASS mailing list archive at Nabble.com.
> _______________________________________________
> Glass mailing list
> [hidden email]
> http://lists.gemtalksystems.com/mailman/listinfo/glass

_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass

BrunoBB

Re: Upgrade Grease behind firewall

Dale,

Thanks for the answer.

The Stone is running OK, now i want to install my application from the Scratch and first thing to do is to install seaside.

From a notebook with internet there are no problems with:
GsDeployer deploy: [
Metacello new
baseline: 'Seaside3';
repository: 'github://GsDevKit/Seaside31:gs_master/repository';
onLock: [:ex | ex honor];
load: 'CI' ].

but we are having some problem behind firewalls.
There is another/script way to install seaside ?

regards
bruno

GLASS mailing list

Re: Upgrade Grease behind firewall

On 06/27/2016 11:10 AM, BrunoBB via Glass wrote:

> Dale,
>
> Thanks for the answer.
>
> The Stone is running OK, now i want to install my application from the
> Scratch and first thing to do is to install seaside.
>
> From a notebook with internet there are no problems with:
> GsDeployer deploy: [
> Metacello new
> baseline: 'Seaside3';
> repository: 'github://GsDevKit/Seaside31:gs_master/repository';
> onLock: [:ex | ex honor];
> load: 'CI' ].
>
> but we are having some problem behind firewalls.
> There is another/script way to install seaside ?

Yes ... when you built the stone, did you install tODE? My answer and
follow-on questions depend upon what is included in the stone ... as I
mentioned, you can clone the Seaside3 github repository to disk outside
the firewall and then copy the github repo to your GsDevKit_home
installation ($GS_HOME/shared/repos) ... but what you do after that is a
function of what you have installed in the stone.

Also which hich Seaside adaptors do you plan on using?

Dale
_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass

BrunoBB

Re: Upgrade Grease behind firewall

Dale,

createClient tode1 |& tee -a $GS_HOME/install.log
This command was the last to be executed.

The stone has no Seaside packages installed.

I do not know if you need more information ?

regards
bruno

GLASS mailing list

Re: Upgrade Grease behind firewall

How did you create the stone that you are using behind the firewall?

Could you give me the explicit things you did?

I have no clue as to how your stone got created and thus I have no way
to know what to tell you what to do. If you are using tODE I would ask
you to do a CTL-SHIFT-P on the `project list` window and send me the
result --- then I would know exactly what you have installed in the
stone... but right now I don't know what you have and if you don't have
tODE installed then it is much more difficult for me to tell you how to
produce the information that I want from you and it is more difficult to
tell you how to load Seaside3 from git repositories ... this is the
reason that I created tODE in the first place ...

Dale

On 06/27/2016 12:37 PM, BrunoBB via Glass wrote:

> Dale,
>
> createClient tode1 |& tee -a $GS_HOME/install.log
> This command was the last to be executed.
>
> The stone has no Seaside packages installed.
>
> I do not know if you need more information ?
>
> regards
> bruno
>
>
>
> --
> View this message in context: http://forum.world.st/Upgrade-Grease-behind-firewall-tp4903625p4903709.html
> Sent from the GLASS mailing list archive at Nabble.com.
> _______________________________________________
> Glass mailing list
> [hidden email]
> http://lists.gemtalksystems.com/mailman/listinfo/glass

_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass

GLASS mailing list

Re: Upgrade Grease behind firewall

In reply to this post by BrunoBB

On 6/27/16 12:37 PM, BrunoBB via Glass wrote:

Dale,

createClient tode1 |& tee -a $GS_HOME/install.log
This command was the last to be executed.

This creates a tODE client but not a stone ...

I'm curious how you created the stone.


The stone has no Seaside packages installed.

If you were outside a firewall, I would tell you to run the following command to create a stone that had Seaside3.2 installed:

createStone -u
      http://gsdevkit.github.io/GsDevKit_home/Seaside32.ston -i Seaside3
      -l Seaside3 Seaside3 3.3.1

      

      The -u option downloads the default project entry for Seaside3.
      The default project entry for Seaside3.2 looks like the following:

      

      ^ TDProjectSpecEntryDefinition new

          baseline: 'Seaside3'

            repository: '

github://SeasideSt/Seaside:master/repository

'

            loads: #('Zinc' 'Development' 'Examples');

          installScript: 'project clone --https --local Seaside3

            project install --local
      --url=http://gsdevkit.github.io/GsDevKit_home/GsApplicationTools.ston';

          gitCheckout: 'master';

          status: #(#'inactive');

          locked: false;

          yourself

      

      and contains instructions for not only installing Seaside3.2 into
      a stone, but includes instructions for cloning the Seaside3
      project and the GsApplicationTools project to the local
      GsDevKit_home repositories.... Once a project entry has been
      downloaded into the $GS_HOME/sys/local/server/projects directory,
      subsequent stones can be built using the following:

createStone -l Seaside3 Seaside3 3.3.1

      

      and the locally cloned Seaside repository will be used for the
      load ... 

      

      If you want to avoid the need to get ssh downloads working behind
      your firewall, I suggest that you first create a stone with
      everything you want loaded into it starting with the above Seaside
      stone (which version of Seaside 3 are you using?) --- and use
      project entries for all of the github projects that you may be
      using ... using project entries means that you will have local
      clones of the projects and when moved behind the firewall you will
      be able to build a stone without needing to hit the network for
      loading the github repos ... given the fact that you've apparently
      solved the the "http through the firewall problem" having local
      clones of the github repositories is exactly what you need ...

      

      Dale

_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass

BrunoBB

Re: Upgrade Grease behind firewall

Dale.

Finally i have installed Seaside in GemStone but i have made a very ugly thing :) ;)

It turns out that the problem was in method:
MetacelloGemStonePlatform>>extractHTTPHeader:do:

Is still under "investigation" why this happend. Inside GS the net packet is like:
HTTP/1.0 200 Connection established

HTTP/1.1 200 OK
Server: GitHub.com
.........

But if i do a curl in the command line the answer is like:
HTTP/1.1 200 OK
Server: GitHub.com
......

So in MetacelloGemStonePlatform>>extractHTTPHeader:do:
I changed:
line := aStream nextLine."strip status"
with:
line := aStream nextLine; nextLine; nextLine. "strip status"

And the problem was fixed Seaside is running and working now.
The person of networking told me that the Reverse Proxy or any other element does not change any net packet but he is not 100% sure.

Of course the problem is 100% here. But now has been fixed !

Regards,
Bruno

GLASS mailing list

Re: Upgrade Grease behind firewall

Bruno,

Since GemStone also calls /usr/bin/curl this is very odd. There _must_
be a difference between the full command line used by GemStone and your
test ... otherwise how can it be explained that curl itself gives two
different answers?

Dale

On 6/30/16 10:04 AM, BrunoBB via Glass wrote:

> Dale.
>
> Finally i have installed Seaside in GemStone but i have made a very ugly
> thing :) ;)
>
> It turns out that the problem was in method:
> MetacelloGemStonePlatform>>extractHTTPHeader:do:
>
> Is still under "investigation" why this happend. Inside GS the net packet is
> like:
> HTTP/1.0 200 Connection established
>
> HTTP/1.1 200 OK
> Server: GitHub.com
> .........
>
> But if i do a curl in the command line the answer is like:
> HTTP/1.1 200 OK
> Server: GitHub.com
> ......
>
> So in MetacelloGemStonePlatform>>extractHTTPHeader:do:
> I changed:
> line := aStream nextLine."strip status"
> with:
> line := aStream nextLine; nextLine; nextLine. "strip status"
>
> And the problem was fixed Seaside is running and working now.
> The person of networking told me that the Reverse Proxy or any other element
> does not change any net packet but he is not 100% sure.
>
> Of course the problem is 100% here. But now has been fixed !
>
> Regards,
> Bruno
>
>
>
>
> --
> View this message in context: http://forum.world.st/Upgrade-Grease-behind-firewall-tp4903625p4904279.html
> Sent from the GLASS mailing list archive at Nabble.com.
> _______________________________________________
> Glass mailing list
> [hidden email]
> http://lists.gemtalksystems.com/mailman/listinfo/glass

_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass