Add option to override default site path

[rmccue]

For sites where the default site isn't the root of the local URL, it'd be useful to have a way to override the default that we provide to wp-cli. e.g. if your default site is at example.altis.dev/en/, you currently need to pass the URL every time.

I'd suggest we add a default_site_url option (e.g. "default_site_url": "https://example.altis.dev/en/"), or a default_site_path option (e.g. "default_site_path": "/en/") to override this.

---

Acceptance Criteria

• When specifying a default site URL as "default_site_url": "example.altis.dev/en" in composer.json, composer server cli commands work without passing --url.
• When not explicitly specifying a default site URL in composer.json, composer server cli commands use a default URL based on the domain setting
• Given the above, CI builds also work
• Passing a --url flag for a different sub site still works.
• Tachyon URLs are still generated as example.altis.dev/tachyon and continue to function.
• Perform manual testing on this with subsites at / and /en/ to check the default is working. (No automated testing required, as we don't have a framework in place.)
• Record the process of testing into the ticket so that it can be replicated later.
• Document in Local Server's docs about config options.

---

For Altis Team Use

Ready for Work Checklist

Is this ticket ready to be worked on? See
the Play Book Definition of Ready.

• Is the title clear?
• Is the description clear and detailed enough?
• Are acceptance criteria listed?
• Have any dependencies been identified? (Optional)
• Have any documentation/playbook changes been identified? (Optional)
• Is an estimate or time box assigned?
• Is a priority label assigned?
• Is this ticket added to a milestone?
• Is this ticket added to an epic? (Optional)

Completion Checklist

Is this ticket done? See
the Play Book Definition of Done.

• Has the acceptance criteria been met?
• Is the documentation updated (including README)?
• Do any code/documentation changes meet project standards?
• Are automatic tests in place to verify the fix or new functionality?
  • Or are manual tests documented (at least on this ticket)?
• Are any Playbook/Handbook pages updated?
• Has a new module release (patch/minor) been created/scheduled?
• Have the appropriate backport labels been added to the PR?
• Is there a roll-out (and roll-back) plan if required?

[rmccue]

This looks like the main place we generate the URL:

altis-local-server/inc/composer/class-command.php

Lines 1143 to 1160 in 3b492e9

	/**
	* Get the name of the project for the local subdomain
	*
	* @return string
	*/
	protected function get_project_url() : string {
	$config = $this->get_composer_config();
	if ( $this->is_using_codespaces() ) {
	return 'https://' . getenv( 'CODESPACE_NAME' ) . '-80.githubpreview.dev/';
	}
	$tld = $this->get_project_tld();
	$site_url = sprintf( static::set_url_scheme( 'https://%s%s/' ),
	$this->get_project_subdomain(),
	$tld ? '.' . $tld : ''
	);
	return $site_url;
	}

However, this is also used in the Docker compose generator for the Tachyon URL, so overriding this would break Tachyon URLs (e.g. would be https://example.altis.dev/en/tachyon/ which would break), so needs something slightly different. Possibly the Docker compose should be updated to use the hostname instead of the URL, but needs checking with the Codespaces support too.

[ferschubert-hm]

Hey team! Please add your planning poker estimate with Zenhub @jerico @kovshenin @mikelittle @wisyhambolu

[ferschubert-hm]

Please add your planning poker estimate with Zenhub @filter182

[jerico]

@ferschubert-hm @filter182 Please add you planning poker estimate

[jerico]

@mikelittle Please add the note how to set it up on Altis