6.4 KiB
WWW Deployment Manifest
This document lists the files under www/ in the current deployment set that should be copied to the remote staging path:
/home/marco/regalamiunsorriso/incoming/www
Deployment Set
All files in this rollout are deployed from the current working tree.
New Files
- None in this rollout.
Updated Files
www/mailMessage/noMorePic.htmlwww/mailMessage/noMorePic.txtwww/mailMessage/noMorePicCc.htmlwww/mailMessage/noMorePicScad.htmlwww/mailMessage/noMorePicScad.txtwww/mailMessage/perScadereMsg.htmlwww/mailMessage/userMsg_itCC - Copy.htmlwww/mailMessage/userMsg_itCC.html
Remote Copy Target
- Source root:
K:\various\regalamiunsorriso - Remote host:
marco@83.149.164.4:410 - Remote staging path:
/home/marco/regalamiunsorriso/incoming/www - Remote live path:
/home/sites/regalamiunsorriso/www - Total files in this manifest:
8
Transfer Method
- Stage by streaming a tar archive over SSH and extracting it into
/home/marco/regalamiunsorriso/incomingso thewww/...directory structure is preserved. - Promote with
/home/marco/promote-file.shthroughsudo tcshso the live destination keeps its required owner, group, and mode.
Verification Expectations
- Verify staged files with
ls -landcksum. - Verify live files with
ls -l,stat -f, andcksum. - Existing destination files should retain their original metadata after promotion.
Known Shell Quirks
- The remote login shell behaves as
tcsh, so POSIX shell loops fail unless run throughsh -c. - The server
shdoes not support-l, so usesh -c, notsh -lc. - Direct SSH plus tar works reliably on this host; MCP SSH was previously unreliable and is avoided.
- PowerShell quoting can break remote helper commands for paths with spaces; using
ssh ... --%passes verification commands through cleanly. - Direct remote use of
2>/dev/null, pipelines, and escaped parentheses can still fail undertcshwithAmbiguous output redirect; for read-only investigation, prefer small single-purpose SSH commands or wrap the full payload in remotesh -c. - If PowerShell shows the continuation prompt
? >, the quoting failed locally before the command reached the server. Cancel it and rerun a simpler command.
Mail Template Reconnaissance
Read-only investigation on 83.149.164.4 on 2026-04-16 found that mail content is not determined only by the files in www/mailMessage.
Mail Template Directories Found On Server
- Live rollout target:
/home/sites/regalamiunsorriso/www/mailMessage - Staging copy:
/home/marco/regalamiunsorriso/incoming/www/mailMessage - Older duplicate tree:
/home/sites/regalamiunsorriso/wwwLang/mailMessage - Archived duplicate tree:
/home/sites/regalamiunsorriso/wwwOld/www/mailMessage
Representative checksum comparisons confirmed that www/mailMessage and wwwLang/mailMessage currently differ:
noMorePic.html: live2188047161 3645,wwwLang2803737061 3775userMsg_itCC.html: live324589227 5628,wwwLang429470199 4921
Runtime Resolution Path
- The Java application lives under
/home/sites/regalamiunsorriso/rus/WEB-INF. - Local source code shows
DBAdapter.getDocBase()returnsgetParm("DOCBASE").getTesto(). - Local source code shows
Parm.findByCodice()executesselect A.* from PARM AS A where A.codice='...'. - Local source code also shows the mail templates are located through
Parmvalues such asMAIL_REG,MAIL_NO_MORE,MAIL_NO_MORE_SCAD, andMAIL_MSG_PATH_MAILER. - Local
pg_src/com/ablia/pg/Users.javaseeds default values forMAIL_MSG_RINNOVOasmailMessage/rinnovoMsg.htmlandMAIL_MSG_COUPON_OMAGGIOasmailMessage/couponOmaggioMsg.html. - On the live server,
/home/sites/regalamiunsorriso/rus/WEB-INF/classes/dbcomuni.properties,rus.properties, andtruckservice.propertiesall containUSE_PARM_HT=true, which indicates the application expects runtime values from theParmstore.
Implication:
Changing a file in www/mailMessage is not enough to guarantee a changed outbound message. The live Parm data determines at least:
- the effective
DOCBASE - which mail template filename is used for each message type
- the generic mailer template root via
MAIL_MSG_PATH_MAILER
If reports say old messages are still being sent, the next thing to verify is the live Parm row values for DOCBASE, MAIL_REG, MAIL_NO_MORE, MAIL_NO_MORE_SCAD, MAIL_MSG_PATH_MAILER, and any related per-feature mail parameters.
Useful Live App Configuration
- Main webapp DB connection from
rus/WEB-INF/web.xml:dbDriver=3database=//localhost/pguser=rootpassword=root
- Secondary app properties from
rus/WEB-INF/classes/truckservice.properties:dbDriver=3dbName=//localhost/truckserviceuser=rootpassword=root
- Local source code in
DriversJdbc.javamapsdbDriver=3to MySQL Connector/J (jdbc:mysql). - Tomcat is running under
jsvcand is listening on*:8080with AJP on127.0.0.1:8009.
Read-Only DB Access Attempts
- The host has PHP CLI at
/usr/local/bin/phpwithmysqli,mysqlnd,PDO, andpdo_mysqlenabled. - No
mysqlormariadbclient binary was found in the shell path. - A read-only PHP probe over SSH is viable by piping a local script into remote PHP:
- This worked for plain PHP execution and is the safest known way to attempt SQL reads without creating files on the server.
- Live connection attempts behaved as follows:
mysqli('localhost', 'root', 'root', 'pg')failed withNo such file or directory.mysqli('127.0.0.1', 'root', 'root', 'pg')failed withConnection refused.
sockstat -4 -lshowed no listener on MySQL port3306.sockstat -u -land targeted socket checks did not reveal a visible MySQL Unix socket under/var/run,/tmp,/usr/local/var, or/var/db/mysql.- Current conclusion: the application configuration indicates MySQL, but direct SQL access from the current shell is not yet available. The webapp may rely on a non-obvious socket path, a jailed/internal service path, or a runtime environment not exposed to the
marcoshell.
Recon Scope Notes
- The
RUSentry under/home/sites/regalamiunsorrisois a symlink to/mnt/da1/foto. - That tree appears to be photo/archive storage and produced permission noise during reconnaissance.
- It was not needed to identify the email-template resolution path and should be ignored for future mail-template investigations unless the task explicitly involves media storage.