Symfony Profiler

{
    "@context": [
        "https:\/\/join-lemmy.org\/context.json",
        "https:\/\/www.w3.org\/ns\/activitystreams"
    ],
    "actor": "https:\/\/lemmy.world\/c\/selfhosted",
    "to": [
        "https:\/\/www.w3.org\/ns\/activitystreams#Public"
    ],
    "object": {
        "id": "https:\/\/lemmy.dbzer0.com\/activities\/update\/b5a51e0c-9f25-40b7-aa76-42b0dc743e88",
        "actor": "https:\/\/lemmy.dbzer0.com\/u\/mic_check_one_two",
        "@context": [
            "https:\/\/join-lemmy.org\/context.json",
            "https:\/\/www.w3.org\/ns\/activitystreams"
        ],
        "to": [
            "https:\/\/www.w3.org\/ns\/activitystreams#Public"
        ],
        "object": {
            "type": "Note",
            "id": "https:\/\/lemmy.dbzer0.com\/comment\/21401292",
            "attributedTo": "https:\/\/lemmy.dbzer0.com\/u\/mic_check_one_two",
            "to": [
                "https:\/\/www.w3.org\/ns\/activitystreams#Public"
            ],
            "cc": [
                "https:\/\/lemmy.world\/c\/selfhosted",
                "https:\/\/lemmy.dbzer0.com\/u\/TheBlindPew"
            ],
            "content": "<p>A stack is a group of containers that were all started together via a docker-compose.yml file. You can name the stack and have all of the containers dropped down below it. Compose is simply a straightforward way to ensure your containers all boot with the same parameters each time.<\/p>\n<p>Instead of needing to remember all of the various arguments for each container, you simply note them in the compose file and run that. Docker Compose reads the file and runs the containers with the various arguments.<\/p>\n<p>Moving from docker to docker-compose is the single largest ease-of-use change I made in my setup. If you want some help in how to use it, I can post a quick example and some instructions on setting it up. You would use <code>cd [directory with your docker-compose.yml]<\/code> to select the proper directory, then <code>docker-compose up -d<\/code> to run the compose file.<\/p>\n<p>Updating would be <code>docker-compose down<\/code> to stop the stack, <code>docker-compose pull<\/code> to pull updated images, <code>docker-compose up -d<\/code> to start your stack again, then <code>docker image prune -f<\/code> to delete the old (now outdated and unused) images.<\/p>\n",
            "inReplyTo": "https:\/\/lemmy.dbzer0.com\/comment\/21397591",
            "mediaType": "text\/html",
            "source": {
                "content": "A stack is a group of containers that were all started together via a docker-compose.yml file. You can name the stack and have all of the containers dropped down below it. Compose is simply a straightforward way to ensure your containers all boot with the same parameters each time. \n\nInstead of needing to remember all of the various arguments for each container, you simply note them in the compose file and run that. Docker Compose reads the file and runs the containers with the various arguments.\n\nMoving from docker to docker-compose is the single largest ease-of-use change I made in my setup. If you want some help in how to use it, I can post a quick example and some instructions on setting it up. You would use ``cd [directory with your docker-compose.yml]`` to select the proper directory, then ``docker-compose up -d`` to run the compose file. \n\nUpdating would be ``docker-compose down`` to stop the stack, ``docker-compose pull`` to pull updated images, ``docker-compose up -d`` to start your stack again, then ``docker image prune -f`` to delete the old (now outdated and unused) images.",
                "mediaType": "text\/markdown"
            },
            "published": "2025-09-15T16:21:14.104081Z",
            "updated": "2025-09-15T16:38:43.514101Z",
            "tag": [
                {
                    "href": "https:\/\/lemmy.dbzer0.com\/u\/TheBlindPew",
                    "name": "@TheBlindPew@lemmy.dbzer0.com",
                    "type": "Mention"
                }
            ],
            "distinguished": false,
            "language": {
                "identifier": "en",
                "name": "English"
            },
            "audience": "https:\/\/lemmy.world\/c\/selfhosted",
            "attachment": []
        },
        "cc": [
            "https:\/\/lemmy.world\/c\/selfhosted",
            "https:\/\/lemmy.dbzer0.com\/u\/TheBlindPew"
        ],
        "tag": [
            {
                "href": "https:\/\/lemmy.dbzer0.com\/u\/TheBlindPew",
                "name": "@TheBlindPew@lemmy.dbzer0.com",
                "type": "Mention"
            }
        ],
        "type": "Update",
        "audience": "https:\/\/lemmy.world\/c\/selfhosted"
    },
    "cc": [
        "https:\/\/lemmy.world\/c\/selfhosted\/followers"
    ],
    "type": "Announce",
    "id": "https:\/\/lemmy.world\/activities\/announce\/update\/8465a003-5f62-4727-a99c-8a76cdc0f667"
}

{"@context":["https://join-lemmy.org/context.json","https://www.w3.org/ns/activitystreams"],"actor":"https://lemmy.world/c/selfhosted","to":["https://www.w3.org/ns/activitystreams#Public"],"object":{"id":"https://lemmy.dbzer0.com/activities/update/b5a51e0c-9f25-40b7-aa76-42b0dc743e88","actor":"https://lemmy.dbzer0.com/u/mic_check_one_two","@context":["https://join-lemmy.org/context.json","https://www.w3.org/ns/activitystreams"],"to":["https://www.w3.org/ns/activitystreams#Public"],"object":{"type":"Note","id":"https://lemmy.dbzer0.com/comment/21401292","attributedTo":"https://lemmy.dbzer0.com/u/mic_check_one_two","to":["https://www.w3.org/ns/activitystreams#Public"],"cc":["https://lemmy.world/c/selfhosted","https://lemmy.dbzer0.com/u/TheBlindPew"],"content":"<p>A stack is a group of containers that were all started together via a docker-compose.yml file. You can name the stack and have all of the containers dropped down below it. Compose is simply a straightforward way to ensure your containers all boot with the same parameters each time.</p>\n<p>Instead of needing to remember all of the various arguments for each container, you simply note them in the compose file and run that. Docker Compose reads the file and runs the containers with the various arguments.</p>\n<p>Moving from docker to docker-compose is the single largest ease-of-use change I made in my setup. If you want some help in how to use it, I can post a quick example and some instructions on setting it up. You would use <code>cd [directory with your docker-compose.yml]</code> to select the proper directory, then <code>docker-compose up -d</code> to run the compose file.</p>\n<p>Updating would be <code>docker-compose down</code> to stop the stack, <code>docker-compose pull</code> to pull updated images, <code>docker-compose up -d</code> to start your stack again, then <code>docker image prune -f</code> to delete the old (now outdated and unused) images.</p>\n","inReplyTo":"https://lemmy.dbzer0.com/comment/21397591","mediaType":"text/html","source":{"content":"A stack is a group of containers that were all started together via a docker-compose.yml file. You can name the stack and have all of the containers dropped down below it. Compose is simply a straightforward way to ensure your containers all boot with the same parameters each time. \n\nInstead of needing to remember all of the various arguments for each container, you simply note them in the compose file and run that. Docker Compose reads the file and runs the containers with the various arguments.\n\nMoving from docker to docker-compose is the single largest ease-of-use change I made in my setup. If you want some help in how to use it, I can post a quick example and some instructions on setting it up. You would use ``cd [directory with your docker-compose.yml]`` to select the proper directory, then ``docker-compose up -d`` to run the compose file. \n\nUpdating would be ``docker-compose down`` to stop the stack, ``docker-compose pull`` to pull updated images, ``docker-compose up -d`` to start your stack again, then ``docker image prune -f`` to delete the old (now outdated and unused) images.","mediaType":"text/markdown"},"published":"2025-09-15T16:21:14.104081Z","updated":"2025-09-15T16:38:43.514101Z","tag":[{"href":"https://lemmy.dbzer0.com/u/TheBlindPew","name":"@TheBlindPew@lemmy.dbzer0.com","type":"Mention"}],"distinguished":false,"language":{"identifier":"en","name":"English"},"audience":"https://lemmy.world/c/selfhosted","attachment":[]},"cc":["https://lemmy.world/c/selfhosted","https://lemmy.dbzer0.com/u/TheBlindPew"],"tag":[{"href":"https://lemmy.dbzer0.com/u/TheBlindPew","name":"@TheBlindPew@lemmy.dbzer0.com","type":"Mention"}],"type":"Update","audience":"https://lemmy.world/c/selfhosted"},"cc":["https://lemmy.world/c/selfhosted/followers"],"type":"Announce","id":"https://lemmy.world/activities/announce/update/8465a003-5f62-4727-a99c-8a76cdc0f667"}