@webship.co/workspace-godaddy 1.0.10 → 1.0.12
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -86,3 +86,17 @@ bash cmd-tools-godaddy.sh <project> --push
|
|
|
86
86
|
- One project at a time, named by the person.
|
|
87
87
|
- What the command prints about a refused credential is a finding: report it, do not work around it.
|
|
88
88
|
- Say what was not run. A deploy you did not see end is not deployed.
|
|
89
|
+
|
|
90
|
+
## The book
|
|
91
|
+
|
|
92
|
+
For any automated functional testing in this work (a Gherkin feature, a step definition, choosing a
|
|
93
|
+
step, a test run and its failures), read the book *Automated Functional Testing Recipes* first.
|
|
94
|
+
|
|
95
|
+
- **Where.** Use the first that exists: `.claude/automated-functional-testing-recipes/` in the project,
|
|
96
|
+
`~/.claude/automated-functional-testing-recipes/` (installed by webship/webship-js-ai-agent,
|
|
97
|
+
webship/webship-js-skills or webship/ai-agents), or
|
|
98
|
+
https://github.com/webship/webship-js-ai-agent/tree/2.0.x/automated-functional-testing-recipes
|
|
99
|
+
- **How.** Its `README.md` first, then the chapter that matches the task (one file per chapter,
|
|
100
|
+
named by its subject), not the single complete file.
|
|
101
|
+
- **Which wins.** The installed webship-js package and the step pack are the source of truth for
|
|
102
|
+
step phrasing. When they differ from the book, follow them and say so.
|
|
@@ -6,6 +6,7 @@ Get the site <project> ready to deploy to GoDaddy, and give me the deploy line
|
|
|
6
6
|
# ~/workspace/<folder> · container-based (DDEV by default) · <folder> is the sites folder of <project>
|
|
7
7
|
# do not deploy: the deploy asks for a confirmation in a terminal and that is mine to give
|
|
8
8
|
# never print a token or a key; link nothing, pull nothing
|
|
9
|
+
# a feature to write or a run to read: the book Automated Functional Testing Recipes first (its README.md, then the matching chapter), from .claude/automated-functional-testing-recipes/ in the project, ~/.claude/automated-functional-testing-recipes/ or https://github.com/webship/webship-js-ai-agent/tree/2.0.x/automated-functional-testing-recipes
|
|
9
10
|
|
|
10
11
|
1. cd ~/workspace/<folder> ; bash cmd-tools-godaddy.sh <project>
|
|
11
12
|
stop if it is not linked, and show me the line it prints for linking
|
|
@@ -106,3 +106,17 @@ bash core/scripts/plugins.sh --check godaddy # the commands
|
|
|
106
106
|
- **An environment here is a host name**: the linked domain, or one of its A or CNAME records.
|
|
107
107
|
- **A deploy is outward-facing.** The command asks before it sends anything, in a terminal: it is
|
|
108
108
|
not a step for an AI assistant to take on its own.
|
|
109
|
+
|
|
110
|
+
## The book
|
|
111
|
+
|
|
112
|
+
For any automated functional testing in this work (a Gherkin feature, a step definition, choosing a
|
|
113
|
+
step, a test run and its failures), read the book *Automated Functional Testing Recipes* first.
|
|
114
|
+
|
|
115
|
+
- **Where.** Use the first that exists: `.claude/automated-functional-testing-recipes/` in the project,
|
|
116
|
+
`~/.claude/automated-functional-testing-recipes/` (installed by webship/webship-js-ai-agent,
|
|
117
|
+
webship/webship-js-skills or webship/ai-agents), or
|
|
118
|
+
https://github.com/webship/webship-js-ai-agent/tree/2.0.x/automated-functional-testing-recipes
|
|
119
|
+
- **How.** Its `README.md` first, then the chapter that matches the task (one file per chapter,
|
|
120
|
+
named by its subject), not the single complete file.
|
|
121
|
+
- **Which wins.** The installed webship-js package and the step pack are the source of truth for
|
|
122
|
+
step phrasing. When they differ from the book, follow them and say so.
|
package/features/godaddy.feature
CHANGED
|
@@ -2,35 +2,40 @@ Feature: The GoDaddy plugin on a project row
|
|
|
2
2
|
Once the plugin is activated and installed, every site row carries the GODADDY menu, and the Plugins
|
|
3
3
|
page lists the plugin with its four steps.
|
|
4
4
|
|
|
5
|
+
@needs-project-dev
|
|
5
6
|
Scenario: A site row offers the GODADDY menu, captioned with its link state
|
|
6
7
|
Given I am on "/dev"
|
|
7
8
|
Then the element ".act-menu-godaddy" should be displayed
|
|
8
9
|
And I should see "GODADDY"
|
|
9
10
|
And the element ".act-menu-godaddy + .act-status" should be displayed
|
|
10
11
|
|
|
12
|
+
@needs-project-dev
|
|
11
13
|
Scenario: An unlinked project's menu opens and says how to link it
|
|
12
14
|
Given I am on "/dev"
|
|
13
15
|
And I click on the element ".project-row .act-menu-godaddy button"
|
|
14
16
|
Then ".uk-dropdown.uk-open" should be visible
|
|
15
17
|
And I should see "Not linked to GoDaddy"
|
|
16
18
|
|
|
17
|
-
|
|
19
|
+
# The Plugins page names each plugin; the package is on the plugin's own page (the row shows it on hover only).
|
|
20
|
+
Scenario: The plugin is listed on the Plugins page, and its own page names its package
|
|
18
21
|
Given I am on "/settings/plugins"
|
|
19
22
|
Then I should see "GoDaddy"
|
|
20
|
-
|
|
23
|
+
When I go to "/settings/plugin/godaddy"
|
|
24
|
+
Then I should see "@webship.co/workspace-godaddy"
|
|
21
25
|
|
|
26
|
+
# The AI folders are searched by name: with every plugin on, a folder lists more than one page of items.
|
|
22
27
|
Scenario: The AI Agents folder lists the agent the plugin ships
|
|
23
|
-
Given I am on "/ai-agents"
|
|
28
|
+
Given I am on "/ai-agents?q=godaddy-deployer"
|
|
24
29
|
Then I should see "godaddy-deployer"
|
|
25
30
|
|
|
26
31
|
Scenario: The AI Skills folder lists the skill the plugin ships
|
|
27
|
-
Given I am on "/ai-skills"
|
|
32
|
+
Given I am on "/ai-skills?q=godaddy-hosting"
|
|
28
33
|
Then I should see "godaddy-hosting"
|
|
29
34
|
|
|
30
35
|
Scenario: The AI Commands folder lists the command the plugin ships
|
|
31
|
-
Given I am on "/ai-commands"
|
|
36
|
+
Given I am on "/ai-commands?q=godaddy-status"
|
|
32
37
|
Then I should see "godaddy-status"
|
|
33
38
|
|
|
34
39
|
Scenario: The AI Prompts folder lists the prompt the plugin ships
|
|
35
|
-
Given I am on "/ai-prompts"
|
|
40
|
+
Given I am on "/ai-prompts?q=godaddy-test-then-deploy"
|
|
36
41
|
Then I should see "godaddy-test-then-deploy"
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@webship.co/workspace-godaddy",
|
|
3
|
-
"version": "1.0.
|
|
3
|
+
"version": "1.0.12",
|
|
4
4
|
"description": "GoDaddy for Webship Workspace: the GODADDY menu on every site row, the domain and its DNS from the GoDaddy API, the hosting account over SSH (get database and files, deploy with rsync, the error log), the GoDaddy console. It carries its AI items, each placed in the workspace folder of its kind: an agent, a skill, a command and a prompt. A provider of @webship.co/workspace-hosting.",
|
|
5
5
|
"main": "dist/src/index.js",
|
|
6
6
|
"types": "dist/src/index.d.ts",
|