#docker port mapping

[codeonedigest]

Docker Container Port Mapping Tutorial for beginners | Docker Port Expose and Port Forwarding

Full Video Link: https://youtu.be/2gie3gpDJUg Hi, a new #video on #dockerportmapping is published on @codeonedigest #youtube channel. Learn docker container port forwarding and docker expose. What is docker port mapping and -p option. Running docker cont

Docker container port mapping and port forwarding. Docker expose attribute in Docker file is used to forward container port to the host machine. Running docker container on custom port. Using docker expose, run the docker application on specific port. How to run docker image on specific port? What is port mapping in docker container? Why docker port mapping is not working? Why containerized…

[gloomwitchwrites]

Tattoo Artist Simon "Ghost" Riley x Female Reader

Chapter Specific Warnings (per the warnings MDNI): canon-typical violence, swearing, angst

Word Count: 3.5k

A/N: Part Twenty-Five of Ink & Needle

Price reveals three possible locations. Task Force 141 infiltrates.

Chapter Twenty-Four // Chapter Twenty-Six

ao3 // main masterlist // ink & needle masterlist

Knuckles pop. Joints crack.

Simon is primed—nerves and muscles alive and firing.

Ready for action.

Ready for blood.

His old life is returning. Not as fragments but through muscle memory. The training never left. It still dwells within him, twisting around tendons and bone like vines strangling a trellis, awakening to revive the man that once was.

"Tell me what you see, Simon."

Captain Price's voice comes from behind, drifting around Simon like lingering cigarette smoke and dirty snow. Silently, Simon observes the spread of information before him.

"These are the possible targets?" asks Simon, his gaze moving from picture to picture.

A small burst of air before the balaclava becomes steam. The abandoned barn they’ve set up shop in is fucking cold even with the generator-backed heaters turned on. But the cold hardly bothers Simon. His bad knee might not like it but the ache is easy to ignore.

On the wall is a massive map of the world. There are pictures of people and places pinned in various locations. Some of the people are crossed out—marked dead. Others are untouched or painted over with a question mark.

"Yes," affirms Price. "Anything familiar?"

Simon shifts his attention away from the wall and to the table in front of him. There are more pictures here—more documents.

A muscle in his neck spasms. "No," growls Simon. "Walsh likely abandoned his old haunts."

Price shrugs. "Maybe. Maybe not."

Two pictures of Walsh stare back at Simon. One is an old photograph from before. Walsh's skin is perfect here—free from burn scars or blemishes. The second photograph is newer but slightly blurry. Walsh wears a black jacket, hood up, face in profile. Even with the burn scars, his face is unmistakable.

"Walsh is prone to paranoia," says Simon, bringing the newest photograph closer. "He had places even I didn't know about."

"That's my point," replies Price. "Walsh trusted you. And yet he still didn't tell you everything."

We are gardens now.

The two of us.

It's easier to forgive an enemy than to forgive a friend.

Simon's fingers twitch with the urge to crush the photograph. Shoving the compulsion down, Simon returns the picture of Walsh to the table. Focusing on the massive board before him, Simon observes each marked location, his mind flipping through the rolodex of information he obtained during his infiltration.

"What makes you think it's one of these three?" asks Simon.

He lightly taps the picture in front of him. It's an aerial photograph of a series of warehouses near the Port of Felixstowe. There are two other ports marked including those of London and Liverpool.

Unease slides like sludge in Simon’s stomach. “Not only are these major ports, two of the three are fucking tourist attractions.” Simon turns on Price, crossing his arms over his chest. “You can tour a naval vessel and then board a cruise ship in a single day at Liverpool. London is the fucking same. Walsh isn’t making moves there.” He points at the picture of Felixstowe. “This is the only plausible of the three. Privately owned. Recent docker worker strikes.” Simon drops his arm. “But I don’t fucking believe that for a bloody second.”

There are other ports marked across Europe and the United States. Walsh likes to move around, never staying in one place too long. Sometimes he’s moving drugs. Sometimes he’s moving weapons. Using the same place of entry is risky with dangerous cargo.

"We have surveillance," replies Captain Price.

Gaz hands Soap a laptop. Johnny takes a seat and taps away at the keyboard, bringing up several video feeds.

"This one is for Felixstowe." Johnny allows the feeds to run for a bit before clicking over to a new set. "Liverpool." He switches again. "And London."

Simon shakes his head, noticing nothing in the grainy footage. "It's too close to home. Too busy. Too regulated."

Price's face remains impassive. “Look closer." He glances at Soap. "Roll them again."

Simon steps up directly next to Johnny's shoulder. Placing one hand on the table, Simon leans in. Johnny pulls up the surveillance feed near Felixstowe first. As it plays, a tiny twist of anxiety curls in his stomach. Are his eyes going to shit?

"You see it now?" asks Price.

"No," says Simon sharply.

Johnny loops the feed and points. "Here, Lt."

Squinting helps but hardly makes things any clearer. "Zoom in."

Johnny pauses the feed and enlarges it enough to give a more focused picture but not enough to render the pixels worthless. From the back of an SUV emerges a man that looks like Walsh. With him is—a woman?

Like a punch to the solar plexus, the wind is knocked out of Simon.

Is that you?

"You see it, Lt?"

"I see it," growls Simon. "Show me the next one."

Johnny repeats each surveillance feed, pausing and zooming in. There is a woman emerging from an SUV in each one, that is unmistakable, but is it you? That part is unclear. The videos aren't distinct enough to show details.

"We think this is her," says Price.

"In three different places?" asks Simon, skeptical.

Hope is a fragile thing. He wants to cling to it, to imagine that this is you he's seeing in all three feeds, but he cannot allow himself to latch onto an idea that may not hold any reality.

The middle of Price's brow creases. "You need to look again, Simon."

Simon slowly straightens himself. All of this feels like a game—Walsh's game.

"The timestamps don't make sense," growls Simon. "They're not even hours apart!"

"Exactly," says Price, stepping closer. "All of them are the same. Except one." Price lightly squeezes Johnny's shoulder. He brings up the first video feed again, the one from Felixstowe. "This one is different," murmurs Price, his gaze focused on the computer screen.

The feed plays and Johnny pauses the image. A small light flicks on in the dark recesses of Simon's mind.

"You see it now, Simon?"

"I see it, Captain."

Of the three, the woman is always alone in the Liverpool and London feeds. In Felixstowe, she isn't. In Felixstowe, there's a man grabbing her upper arm. A man that looks very much like Simon's enemy.

"We don't have confirmation," continues Price, already seeming to know exactly what Simon is thinking.

It doesn't fucking matter if they have confirmation or not. This is a lead. This is something.

"We've already sent recon teams," adds Kyle, breaking his silence.

The pity isn't there anymore. There is only grim determination. They've seen Simon at his lowest, and yet that doesn't matter. They're doing this to take Walsh down but they're also doing it for him.

Gaz glances at the map but he addresses Simon. "Walsh wants us to focus on Felixstowe." He turns attention to Simon. "Which is why we sent recon."

"And recon said different," replies Simon.

Kyle winks. "Exactly."

"Felixstowe is staged." Price moves toward the map. "But Liverpool?" Price turns back to Simon, with a smirk. "Want to know who funded that little transfer for Walsh?"

Walsh has always moved behind the scenes. He always lurks in the dark. Pockets are lined and Walsh obtains what he wants. At its core, big business is greedy. They’ll happily look the other way if they can get what they want and get away with it.

Some of the earlier unease melts, adrenaline replacing the anxiety.

Simon’s question is immediate “Did you bag the fucker?”

“I have a tail on them as we speak.”

“Good,” growls Simon. “Walsh with them?”

“No.”

Even better. It means Simon can deal out his own justice.

Simon exhales, trying to find a sense of calm amongst all this new information. "All I want is Walsh.”

I just want her back.

Simon wants that fucking wanker alive. He wants Walsh to squirm. To suffer. To feed the man his own teeth before making him choke on them.

But even that won’t satiate what Simon truly desires.

You. Only you.

In his arms again. Warm and safe and all his. To know that you will never come to harm again.

Price’s smirk becomes a genuine smile. They’ve been after this man for fucking years, and now Walsh is truly in their grasp.

Nodding toward the map, Price gestures toward it. "Our best guess is this warehouse near the Port of Liverpool."

"Why?" asks Simon. “It’s a haven for tourist.”

“It caters to tourist and occasionally houses the Royal Navy just as much as it brings in and sends out goods.” Price exhales. “It’s busy, yes. But it’s unsuspecting.”

"It's also the only place we've seen Walsh arrive to and leave from," adds Kyle.

Simon shrugs. “Could be a distraction. Make it obvious so we aren’t looking at other possible targets.”

“Could be,” replies Price casually.

“We’ve got him, Lt. And not on surveillance footage.”

"The recon team did," continues Gaz. "Real subtle, too. Like he didn't want to be seen."

Diversion has always been Walsh's specialty. His most devoted followers will do whatever he asks from shooting up a corner store to acting as a body double. The man is a manipulator. A friendly face that says exactly what you want to hear to reinforce your own confirmation bias.

He does it all in the name of power and personal superiority.

Simon turns toward Price. "Are we going after that warehouse?"

Price nods. "Tomorrow."

Darkness is a friend.

A companion. A trained beast. A silent killer.

Simon looks into his scope, checking and rechecking the perimeter of the building. Soap has already disabled the surveillance camera on the western side of the building. To the person watching, they're seeing a continuous loop of nothing.

The building itself isn’t one of those boxy metal buildings you find all over the States. This warehouse is old, made from brick and stone, built when ships were still only made of wood. Marked as a historical location, and yet currently closed to the public.

How bloody fucking convenient.

While the night is cold, the port isn’t empty. There are no cargo ships unloading but there’s a docked Destroyer all lit up across the River Mersey. Tourists and locals move along pedestrian areas, and the nearby arena is awash with light as some musical artist performs.

Life moves. Uninterrupted.

As it should be.

And not one of those souls realize what lurks in the dark.

“Soap. We ready to breach?” comes Price’s voice over comms.

Johnny’s answer is laced with slight static. “You have five minutes until the loop ends.”

Price turns back to look at Simon and Kyle, silently pointing in the direction of the door they’re entering the building through. Johnny is on the roof with two members of the recon team sent earlier.

With rifles raised, the trio move silently across the concrete. Price forms the front while Gaz and Simon take the sides and back. They stay on a swivel, watching Price’s rear as he approached the door.

“Three minutes, Captain,” comes Johnny’s voice over comms.

Behind Simon, there’s a clink of metal meeting metal. Something rattles. Then a soft creak as the service door opens.

“We’re in,” replies Price.

Price eases the door open. He keeps his gaze forward, hand coming up to signal that everything is clear. Simon enters behind Price with Kyle on his heel.

“There are three down the hall,” crackles Johnny’s voice over comms.

Price, Gaz, and Simon move silently down the tight hallway. One side is solid brick, the other treated wood. They pass breakers and switches but no doors. There are a few wall hangings but they’re for the workers who would handle the upkeep.

At a tight turn, Price presses himself against the wall. Simon and Kyle crouch as Price eases a small handheld mirror around the corner. There are only a few feet of hallway remaining before it meets a door that says “EXIT.”

“Where are they, Soap?”

A pause. “Just outside the door. Left.”

Price turns the corner and stops at the door. They form a line, switching off night vision. The door opens, and Price is moving. Simon is right behind him, blood roaring in his ears as he follows his captain.

Simon’s finger hugs the trigger.

A muted pop leaves the chamber.

Dark red bursts in the dim light, painting the wall and nearby mounted lamp. The three men never had a chance. They don’t even make a sound as the lead penetrates their heads and explodes in their skulls.

Price’s voice greets Simon in his earpiece. “Clear.”

“Two near the entrance. Follow the lights.”

The building is utterly silent. It’s all exposed brick and pipes. Distantly, Simon hears water dripping, but it is otherwise quiet like a slumbering monster.

Walsh is here. He fucking has to be. Simon senses it in his gut.

Price takes the two out near the entrance, Simon following behind with an extra bullet for each just to make sure.

“We’re coming up on your right, Captain.”

Johnny appears with one member of the recon team. The other remains on the roof, keeping an eye for any incoming vehicles.

“The bunker is through here,” says Johnny, aiming his weapon at the floor.

“The door is in the bloody floor?” asks Kyle.

Johnny crouches, his gloved hand gently probing the wood. They all watch until his hand pauses, his fingers lightly pressing downward.

There’s a hiss, and then Johnny is lifting, revealing a ladder and a dimly lit hall that Simon cannot see the end of.

Price squeezes the shoulder of the soldier from recon. “Keep a lookout here. Radio if you hear or see anything.”

“Yes, sir.”

Price releases his shoulder and descends first. Johnny heads down next followed by Simon and then Kyle.

They’re going in blind. They do not have the plans or layout of this part of the building. The strangest thing is that it looks brand fucking new. It doesn’t make any sense.

Walsh doesn’t build. He utilizes what’s available and goes from there.

There’s only just enough light to see by and there are no doors except the one at the end of the short hall. They might find a maze. They might find a singular room. There could be walking into a trap or nothing at all.

Simon isn’t sure what worries him more.

But you have to be here. Somewhere.

Price counts down starting with three fingers. At one, he raises his rifle and kicks in the door, charging forward. Heartrate spiking, Simon heads in after him, finger tight on the trigger, ready to burst skulls and shatter bone.

The adrenaline peaks, swarming Simon’s senses.

And then it comes crashing down.

As if falling from a great height, Simon is presented with an entirely different outcome.

The firing end of the rifle drifts downward, his gaze focusing on the singular object in the entire room. It’s a box. A metal tackle box like you’d take on a fishing trip. Above it is a bulb hanging from the ceiling. The light it emits is warm and low like it’s been on for years and is just about ready to give out.

Price, Johnny, and Kyle all walk the perimeter of the room.

“It’s solid fucking concrete!” shouts Johnny, his steps increasing as he drags one gloved hand along the wall.

Price slowly spins. “What the fuck is this place?”

“It’s not a storage warehouse,” says Kyle. “There’s nothing here.”

“A hideout, then?” suggests Johnny. “A bunker?”

“Then where’s the bloody bed?” replies Kyle, voice rising slightly. “There isn’t even a table!”

Simon’s focus is narrowing to a pinpoint.

The tackle box is a deep forest green, the handle black, the latch gold.

He takes a step toward it.

“Don’t touch that, Simon.”

Simon ignores Price’s command. He moves closer.

“Simon!”

“Lt! Don’t touch it!”

It’s a game. This is all Walsh’s game.

Simon comes down to one knee beside the tackle box. It’s old—a little banged up. Somehow, he recognizes it.

His gloved thumb brushes over the metal latch.

“Simon!”

It’s Johnny, but Simon is already moving—already releasing the latch and lifting the lid.

Memory resurfaces, and cold dread twists Simon’s stomach. Scratched into the interior of the lid is a name.

It’s Simon’s father’s name.

The tackle box is his father’s, a relic from a time when there was no abuse and no alcohol. Simon remembers going on fishing trips as a young boy carrying this exact box even though he was far too small to hold it properly. He’d always walk leaning to one side due to the weight.

Then it collected dust in a closet as his father became a monster.

But the box isn’t empty.

There are no fishing hooks or plastic dividers. All of that is gone.

In its place is your hair.

Not much, just a cleanly cut portion no larger than Simon’s pinky. It’s neatly tied with red string. Beneath it is a filmy scrap of paper.

The words face him. Clear and obvious.

She’s not here. Try again, friend.

“Simon.”

A crater in the Earth opens up, swallowing Simon whole. He is descending, falling through an endless hell. Spiraling down, down.

“Simon.”

Johnny’s voice is a distant thing. It’s trying to penetrate, to worm inside and pull Simon out but his mind is flipping.

She’s not here.

Your lock of hair is delicately tied, a regretful solace that rings out into Simon’s subconscious.

Try again, friend.

“Simon!”

Following his name is a rattling of gunfire. It’s not distant. Just over his shoulder. In Simon’s earpiece, someone is rattling off a series of numbers and positions, but Simon isn’t paying attention.

You are not here.

You are—elsewhere.

Lost.

In a place where Simon cannot tread.

An instant passes. Then another. The darkness around him transforms, flipping end over end until everything that Simon knows about himself slips away.

You were supposed to be here. He’s supposed to find you. To bring you back.

But this is a task that Simon clearly cannot handle.

Fingers claw up his esophagus, creep over his tongue, and press against his teeth. It emerges, breaking joints, allowing the darkness Simon feels to burst forth and wrap around him, enshrining him in a bloodlust he hasn’t felt in years.

The rifle tip rises. Simon is running on autopilot, allowing Ghost to take over, to consume every ounce of sanity.

Price, Soap, and Gaz are holding down the door, firing at an enemy that Simon cannot yet see.

His feet are not his own. His hands belong to someone else.

Charging forward, the firing end of the rifle explodes. The enemy on the other side are surprised by his sudden appearance. They faulter for a second, their eyes widening slightly in fear. But it’s enough.

It’s enough.

They are cut down, reaching out, hands pressing against the holes in their bodies as blood pools on the floor.

Simon unloads until he’s empty. Reloads. Empties again.

“Simon!”

The rest of his team follow, but Simon is hungry. A blood beast.

When the lead isn’t enough, he uses his hands.

There are bodies all around him, a trail for Price, Gaz, and Soap to follow.

On he moves, devouring. Slicing and gutting until the blood of his enemies begins to soak into his clothes.

He doesn’t remember ascending. Doesn’t remember resurfacing only to dive right back into the void. With ears ringing and a hint of metal on his tongue, Simon destroys everything in his path.

He is aware of Price, Johnny, and Kyle. They move around him, guns high, picking off everyone they can. Simon moves from enemy to enemy, uncaring of how he kills them. He breaks bones. Breaks teeth. Breaks soul. He stabs and slices, relishing in every anguished sound they make.

It is only when so many have fallen that Simon digs in, wanting to draw out a final blow as if the man before him is Walsh and not a nameless crony. The man sobs, his eyes replaced with Simon’s burrowing thumbs.

“Where is she!” screams Simon. He doesn’t even recognize his own voice. “Where the fuck is she!”

The sob becomes a garbled cry. Bloody. Crimson pools and dribbles from the man’s open mouth.

“Tell me where she is!”

Unresponsive. Dead.

Simon slams the man’s head against the floor.

But it isn’t enough. It will never be enough.

A strangled scream is ripped from Simon as he repeatedly bashes the man’s head into the floor.

Hands are on him, grabbing at his arms, tearing him away. Simon swings, clipping Johnny in the chin.

“Enough!” Price wrestles Simon to his feet, pushing him hard against the wall. “They’re dead, Simon.”

His head pounds, the balaclava moving rapidly into and out of his mouth as he gasps for air.

You’re not here.

You’re not here.

It’s all slipping away. Piercing and sharp and yet so dull that Simon begins to feel numb.

“Simon,” murmurs Price, the middle of his brow creasing.

Try again, friend.

taglist:

@glitterypirateduck @tiredmetalenthusiast @lialacleaf @creamwhxre @theshrikeandcanary

@knight4xmas @jupiternighties @corvusmorte @darling006 @carma-fanficaddict

@emmylous-world @i-feel-violated @mileyraes @miaraei @cherryofdeath

@ferns-fics @tulipsun-flower @miss-mistinguett @ninman82 @waves-against-a-cliff

@eternallyvenus @cinnabeanz @beebeechaos @no-oneelsebutnsu @marispunk

@smileykiddie08 @whisperwispxx @chaostwinsofdestruction @weasleytwins-41 @randomgurl2326

@webmvie @aykxz98 @xxkay15xx @saoirse06 @unhinged-reader-36

@ravenpoe67 @sageyxbabey @mudisgranapat @lulurubberduckie @leed-bbg

@yawning-grave81 @azkza @nishim @voids-universe @iloveslasher

@talooolaaloolla @sadlonelybagel @haven-1307 @itsberrydreemurstuff @kylies-love-letter

[learning-code-ficusoft]

A Beginner’s Guide to Docker: Building and Running Containers in DevOps

Docker has revolutionized the way applications are built, shipped, and run in the world of DevOps. As a containerization platform, Docker enables developers to package applications and their dependencies into lightweight, portable containers, ensuring consistency across environments. This guide introduces Docker’s core concepts and practical steps to get started.

What is Docker? Docker is an open-source platform that allows developers to: Build and package applications along with their dependencies into containers. 

Run these containers consistently across different environments. Simplify software development, deployment, and scaling processes.

 2. Why Use Docker in DevOps? Environment Consistency: Docker containers ensure that applications run the same in development, testing, and production. 

Speed: Containers start quickly and use system resources efficiently. 

Portability: Containers can run on any system that supports Docker, whether it’s a developer’s laptop, an on-premises server, or the cloud. 

Microservices Architecture: Docker works seamlessly with microservices, enabling developers to build, deploy, and scale individual services independently. 

3. Key Docker Components Docker Engine:

 The core runtime for building and running containers.

 Images: A blueprint for containers that include the application and its dependencies. Containers: Instances of images that are lightweight and isolated. 

Dockerfile: A script containing instructions to build a Docker image. 

Docker Hub: A repository for sharing Docker images. 

4. Getting Started with Docker

 Step 1: Install Docker Download and install Docker Desktop for your operating system from Docker’s official site.

Step 2: Write a Dockerfile Create a Dockerfile to define your application environment. 

Example for a Python app: 

dockerfile Edit 

# Use an official Python runtime as a base image FROM python:3.9-slim 

# Set the working directory WORKDIR /app 

# Copy project files COPY . .

# Install dependencies RUN pip install -r requirements.txt # Define the command to run the app CMD [“python”, “app.py”] 

Step 3: Build the Docker Image Run the following command to build the image:

 bash Copy Edit docker build -t my-python-app . 

Step 4: Run the Container Start a container from your image: 

bash

Edit docker run -d -p 5000:5000 my-python-app

 This maps port 5000 of the container to port 5000 on your host machine.

 Step 5: Push to Docker Hub Share your image by pushing it to Docker Hub: bash 

Edit docker tag my-python-app username/my-python-app docker push username/my-python-app

 5. Practical Use Cases in DevOps Continuous Integration/Continuous Deployment (CI/CD): 

Docker is commonly used in pipelines for building, testing, and deploying applications. 

Microservices:

 Each service runs in its own container, isolated from others. 

Scalability: 

Containers can be easily scaled up or down based on demand. 

Testing: 

Test environments can be quickly spun up and torn down using Docker containers. 

6. Best Practices Keep Docker images small by using minimal base images. Avoid hardcoding sensitive data into images; use environment variables instead. 

Use Docker Compose to manage multi-container applications. Regularly scan images for vulnerabilities using Docker’s built-in security tools. 

Conclusion 

Docker simplifies the development and deployment process, making it a cornerstone of modern DevOps practices. By understanding its basics and starting with small projects, beginners can quickly leverage Docker to enhance productivity and streamline workflows.

[qcs01]

Ansible and Docker: Automating Container Management

In today's fast-paced tech environment, containerization and automation are key to maintaining efficient, scalable, and reliable infrastructure. Two powerful tools that have become essential in this space are Ansible and Docker. While Docker enables you to create, deploy, and run applications in containers, Ansible provides a simple yet powerful automation engine to manage and orchestrate these containers. In this blog post, we'll explore how to use Ansible to automate Docker container management, including deployment and orchestration.

Why Combine Ansible and Docker?

Combining Ansible and Docker offers several benefits:

Consistency and Reliability: Automating Docker container management with Ansible ensures consistent and reliable deployments across different environments.

Simplified Management: Ansible’s easy-to-read YAML playbooks make it straightforward to manage Docker containers, even at scale.

Infrastructure as Code (IaC): By treating your infrastructure as code, you can version control, review, and track changes over time.

Scalability: Automation allows you to easily scale your containerized applications by managing multiple containers across multiple hosts seamlessly.

Getting Started with Ansible and Docker

To get started, ensure you have Ansible and Docker installed on your system. You can install Ansible using pip:  pip install ansible

And Docker by following the official Docker installation guide for your operating system.

Next, you'll need to set up an Ansible playbook to manage Docker. Here’s a simple example:

Example Playbook: Deploying a Docker Container

Create a file named deploy_docker.yml:

---

- name: Deploy a Docker container

  hosts: localhost

  tasks:

    - name: Ensure Docker is installed

      apt:

        name: docker.io

        state: present

      become: yes

    - name: Start Docker service

      service:

        name: docker

        state: started

        enabled: yes

      become: yes

    - name: Pull the latest nginx image

      docker_image:

        name: nginx

        tag: latest

        source: pull

    - name: Run a Docker container

      docker_container:

        name: nginx

        image: nginx

        state: started

        ports:

          - "80:80"

In this playbook:

We ensure Docker is installed and running.

We pull the latest nginx Docker image.

We start a Docker container with the nginx image, mapping port 80 on the host to port 80 on the container.

Automating Docker Orchestration

For more complex scenarios, such as orchestrating multiple containers, you can extend your playbook. Here’s an example of orchestrating a simple web application stack with Nginx, a Node.js application, and a MongoDB database:

---

- name: Orchestrate web application stack

  hosts: localhost

  tasks:

    - name: Ensure Docker is installed

      apt:

        name: docker.io

        state: present

      become: yes

    - name: Start Docker service

      service:

        name: docker

        state: started

        enabled: yes

      become: yes

    - name: Pull necessary Docker images

      docker_image:

        name: "{{ item }}"

        tag: latest

        source: pull

      loop:

        - nginx

        - node

        - mongo

    - name: Run MongoDB container

      docker_container:

        name: mongo

        image: mongo

        state: started

        ports:

          - "27017:27017"

    - name: Run Node.js application container

      docker_container:

        name: node_app

        image: node

        state: started

        volumes:

          - ./app:/usr/src/app

        working_dir: /usr/src/app

        command: "node app.js"

        links:

          - mongo

    - name: Run Nginx container

      docker_container:

        name: nginx

        image: nginx

        state: started

        ports:

          - "80:80"

        volumes:

          - ./nginx.conf:/etc/nginx/nginx.conf

        links:

          - node_app

Conclusion

By integrating Ansible with Docker, you can streamline and automate your container management processes, making your infrastructure more consistent, scalable, and reliable. This combination allows you to focus more on developing and less on managing infrastructure. Whether you're managing a single container or orchestrating a complex multi-container environment, Ansible and Docker together provide a powerful toolkit for modern DevOps practices.

Give it a try and see how much time and effort you can save by automating your Docker container management with Ansible!

For more details click www.qcsdclabs.com 

[govindhtech]

Ultimate Guide Cloud Spanner Emulator Testing Integrated!

Integrating Cloud Spanner Emulator Search engines Cloud’s The company database features globally distributed, dependable, very highly scalable, therefore being an ideal choice for applications with critical functions that need consistent and high performance.

To guarantee that Spanner integrates seamlessly into your apps, as a developer, you must do extensive testing. The goal of integration testing is to confirm that, after modifications to individual components, the various parts of a system function as a whole. For Spanner, integration testing guarantees that data activities in your application, such error handling and transactions, are properly communicated with the database.

This article explains how to use GitHub Actions and the Spanner emulator to build up integration testing for Spanner. For the purpose of quickly developing applications supported by a Spanner database, the emulator imitates the behavior of Spanner outside of Google Cloud.

They will test an example Golang backend service that maintains player profiles for a hypothetical game. These ideas may be used to different services and apps in different languages and sectors of the economy.

Here, you testing the “integration” between Spanner and the profile service to make sure code updates to the service will function as intended in a quick feedback loop. Not every service in our stack has undergone complete end-to-end testing. Before going live in production, testing at that level should be conducted using a real staging setup using Spanner.

Integrated inside the platform where her code resides, GitHub Actions automates the running of tests. Like this, other CI/CD systems will function.

Her application, Profile Service, is dependent on Spanner and uses Spanner emulator, a lightweight offline emulation of a Spanner database.

GitHub Activities: Workflow automation GitHub Actions are the ideal choice for her automated integration tests since our service code is kept in a GitHub repository.

Your software development process may be automated using GitHub Actions, which is a component of a continuous integration and delivery (CI/CD) platform.

You may establish and carry out automatic actions that are triggered by code changes or scheduled events thanks to its seamless integration with GitHub repositories.

A local testing environment: The Spanner emulator An very portable utility that operates entirely offline is the Spanner emulator. This eliminates the need for real Spanner instances and allows developers to test their apps against Spanner without paying any cloud fees. This enables quick development cycles and early integration problem discovery.

You should be aware of the following variations and restrictions between a real Spanner database and the Spanner emulator.

Integrity testing setup for the profile service On Github, you can find the code for the example game application. The integration test for the profile service will be examined first, followed by the process that makes use of Github Actions to allow automated integration testing.

The profile-service main_test.go file contains the integration test for the profile service.

The sections listed below are included in this file: Launching Spanner as an emulator. Install the schema and any necessary test data in the database and Spanner instance. Install the Profile service. The actual exams. tidying up once the exams are over Launching the emulator for Spanner They use the test containers-go library as the Spanner emulator is set up as a container image. This configures the emulator container so that may connect with it on mapped port 9010. In order to facilitate communication between the “emulator” container and any container or process having network access, a Docker network is used for networking.

It’s simple to wait until the container is ready before moving on to the next step thanks to the test containers-go package.

As soon as it’s prepared, you create a Golang struct, get the host information, and expose it as an operating system environment variable. These two will be used subsequently to configure the database and instance.

Install the Spanner package and database Now that the emulator is operating, will must configure a test instance and database.

Let’s start by configuring the instance: This creates the instance by using the Spanner instance golang library. The SPANNER_EMULATOR_HOST environment variable has to be set previously for this to function. If not, your Google Cloud project’s Spanner instance would be the one that the Spanner library would be searching for.

They need a schema file for the database setup. It is up to your processes where this schema file originates. During the’make profile-integration’ instructions in the Makefile, you create a copy of the master schema file in this instance. This enables me to get the most current schema pertinent to the profiles of the players.

They can handle schema adjustments in this method so that the emulator can understand them. Without the terminating semicolons, you must transform the schema file into an array of statements.

Launch the service for profiles Here, you are launching the profile service as an additional container that can interface with the simulator by using test containers go. executing the examinations Her integration tests connect to your profile service’s endpoints using the testify assert package.

Read more on Govindhtech.com

[faysalahmed]

Simplifying SQL Server Deployment with Docker Compose

Introduction

Deploying Microsoft SQL Server can sometimes be a daunting task, especially for developers who just want to set up a quick and simple instance for testing or small-scale use. Docker Compose offers a straightforward solution to this problem, allowing you to define and run multi-container Docker applications with ease. In this blog post, we’ll walk through creating a docker-compose.yml file to deploy SQL Server efficiently.

Prerequisites

Before we begin, ensure you have Docker and Docker Compose installed on your system. If not, you can download and install them from the official Docker website.

Crafting the Docker Compose File

Below is a sample docker-compose.yml file designed to run Microsoft SQL Server in a Docker container:

Understanding the Configuration

Let’s break down the components of this configuration file:

version: This specifies the version of Docker Compose to use, which in this case is 3.8.

services: Under this key, we define all the services (containers) we want to run.

sql-server-db: This is the name of our service.

image: This key specifies the Docker image to use. We’re using the latest version of SQL Server 2019.

container_name: We define a custom name for our container for easier reference.

environment: Here, we set necessary environment variables.

SA_PASSWORD: The password for the sa user. Ensure to replace "YourStrong!Passw0rd" with a strong, unique password.

ACCEPT_EULA: This is mandatory and must be set to Y to run SQL Server in a container.

ports: We map port 1433 on the host to port 1433 in the container, which is the default for SQL Server.

volumes: This is crucial for data persistence. We define a volume named sql-server-data mounted at /var/opt/mssql in the container.

volumes: We declare the named volume sql-server-data for use in our service.

Deploying SQL Server with Docker Compose

With the docker-compose.yml file in place, navigate to its directory in the terminal and run the command:

docker-compose up -d

This command will download the specified SQL Server image (if not already downloaded), create a container with the specified settings, and start it in detached mode.

Connecting to SQL Server

Once the container is running, you can connect to the SQL Server instance using any SQL Server client, with the server address as localhost,1433 and the sa user credentials you specified in the docker-compose.yml file.

Conclusion

Docker Compose simplifies the deployment of applications like SQL Server, making it accessible for developers at all levels of expertise. With a simple docker-compose.yml file, you can have a SQL Server instance up and running in minutes, without the hassle of manual installation and configuration. Always ensure to use strong, unique passwords and understand the licensing agreements of the software you deploy. Happy coding!

[mythgrippa-blog]

Day 001 - establishing

Alrighty! Yesterday was productive if I had to say the least, I am glad when I talk to someone who gets my ideas, so I'm involved in the backend along with databases and anything devOps and AI related. My teammate is a stallion!!! I'm so glad there's someone who makes up for my coding skills, its very weird still, I USED TO BE ABLE TO CODE FOR HOURS AND HOURS... okay I think mostly because I used to program for hours either with Java or C++, and bare bone Javascript, so maybe web development wasn't my strong suit.

But I'm good at understanding and making designs for code, so I'm very involved in seeing the bigger picture and he'll just do the painting. Here's a screen shot of how our backend looks like, so I'm brush it up since its a bit of mess right now

I'm using drawio because lucid just wasn't working for me, I kept running out of shapes, I'd say lucid is good when it comes to making final designs but drawio has that technical feel I like.

RabbitMQ is just so sexy oh my goodness, it allows for simple and fast communication between services. Its free tier is enough for what I need.

I want to learn PostgreSQL so bad, but I can't because we're on a time crunch and we'll just switch to MySQL for each service using an SQL database, since there's going to be data replication across these services, to maintain synchronized data across all services, RabbitMQ comes in the rescue. I hope it can handle, but since we'll starting off with a relatively small userbase, I doubt we'll run into problems, but if it happens we run into issues, I think switching to Kafka might be better since it has like faster reads (thanks to fewer systemcalls within its architecture)

Firestore is very useful and easy to setup, that reliability is useful for our messaging and posting of images, and also Firebase storage as well, that's so cool!!! I'm still working on the designs

I'm still working on the schemas using drawsql website, the reason for the SQL is because its easier to model friendships, invitations, requests, way better than a NoSQL solution, I want to see what Neo4j can do but again I'm trying to keep things simple. I'll also switch to drawio for doing the ER diagrams because drawSQL has limits and I'm a cheapskate

I made use of freesqldatabase.com for a temporary online database we can quickly use, but this limits the choices for ORMs, since we're using NodeJS we can't make use of Prisma since it requires permissions/privileges that the website doesn't offer, but I'm working on making use of google cloud's free e2 instances to host the database, and if that works we finally have our development database!

I still haven't talked to my client, I'd rather someone from frontend do it, I hope they can finally start working together because I can't with this leadership biz! I am reading this leadership guide book, hopefully I learn something.

I've been also looking at buying some light novels for either rezero or overlord, boy boy boy which do I get??? I honestly don't know, but I"ll figure it out later. I can't wait to go a pawn shop and see what cheap board games I can buy, I'm so excited! But that will be a while.

Well my goals today are simple:

Finalize the schemas for the SQL databases and deploy the databases (or I can be cheap and deploy one instance and host 2 databases :D running two docker containers that have mysql on the same e2 instance and then mapping their default 3306 ports to two ports on the instance and then connecting globally! That's so brilliant I'm so cheap HAHAHAHAHA!!!!!!)

Draw up class diagrams for each service, making use of proper design patterns to make the code more neat

Have a meeting with my guy again and see where we go from there

Thanks again for reading my whatever this is, but its really fun hopefully I don't burn out from writing this much so early

[codeonedigest]

(via Docker Container Port Mapping Tutorial for beginners | Docker Port Expose and Port Forwarding)

Full Video Link: https://youtu.be/2gie3gpDJUg

 Hi, a new #video on #dockerportmapping is published on @codeonedigest #youtube channel. Learn docker container port forwarding and docker expose. What is docker port mapping and -p option. Running docker container on custom port.

  @java #java #awscloud @awscloud @AWSCloudIndia #Cloud #CloudComputing @YouTube #youtube #azure #msazure #microsoftazure  #dockerportmapping #dockerportforwarding #rundockercontaineroncustomport #dockercontainerportmapping #dockerportmappingexplained #dockerportmappingnotworking #dockerportmappingvsexpose #dockerportmappingtutorial #dockercomposeportmapping #portmappinginrunningdockercontainer #dockercontainerportmappingexplained #dockercontainerportnotexposed #dockercontainerportchange #dockercontainerportforwardingnotworking #updatedockercontainerportainer #dockerportforwardingrunningcontainer #dockerportforwardingexistingcontainer #dockerportforwardingdoesn’twork #dockercontainerportsexplained #docker #dockertutorial #dockertutorialforbeginners #whatisdocker #dockercompose #dockerandKubernetes

[hydralisk98]

hydralisk98′s web projects tracker:

Core principles=

Fail faster

‘Learn, Tweak, Make’ loop

This is meant to be a quick reference for tracking progress made over my various projects, organized by their “ultimate target” goal:

(START)

(Website)=

Install Firefox

Install Chrome

Install Microsoft newest browser

Install Lynx

Learn about contemporary web browsers

Install a very basic text editor

Install Notepad++

Install Nano

Install Powershell

Install Bash

Install Git

Learn HTML

Elements and attributes

Commenting (single line comment, multi-line comment)

Head (title, meta, charset, language, link, style, description, keywords, author, viewport, script, base, url-encode, )

Hyperlinks (local, external, link titles, relative filepaths, absolute filepaths)

Headings (h1-h6, horizontal rules)

Paragraphs (pre, line breaks)

Text formatting (bold, italic, deleted, inserted, subscript, superscript, marked)

Quotations (quote, blockquote, abbreviations, address, cite, bidirectional override)

Entities & symbols (&entity_name, &entity_number, &nbsp, useful HTML character entities, diacritical marks, mathematical symbols, greek letters, currency symbols, )

Id (bookmarks)

Classes (select elements, multiple classes, different tags can share same class, )

Blocks & Inlines (div, span)

Computercode (kbd, samp, code, var)

Lists (ordered, unordered, description lists, control list counting, nesting)

Tables (colspan, rowspan, caption, colgroup, thead, tbody, tfoot, th)

Images (src, alt, width, height, animated, link, map, area, usenmap, , picture, picture for format support)

old fashioned audio

old fashioned video

Iframes (URL src, name, target)

Forms (input types, action, method, GET, POST, name, fieldset, accept-charset, autocomplete, enctype, novalidate, target, form elements, input attributes)

URL encode (scheme, prefix, domain, port, path, filename, ascii-encodings)

Learn about oldest web browsers onwards

Learn early HTML versions (doctypes & permitted elements for each version)

Make a 90s-like web page compatible with as much early web formats as possible, earliest web browsers’ compatibility is best here

Learn how to teach HTML5 features to most if not all older browsers

Install Adobe XD

Register a account at Figma

Learn Adobe XD basics

Learn Figma basics

Install Microsoft’s VS Code

Install my Microsoft’s VS Code favorite extensions

Learn HTML5

Semantic elements

Layouts

Graphics (SVG, canvas)

Track

Audio

Video

Embed

APIs (geolocation, drag and drop, local storage, application cache, web workers, server-sent events, )

HTMLShiv for teaching older browsers HTML5

HTML5 style guide and coding conventions (doctype, clean tidy well-formed code, lower case element names, close all html elements, close empty html elements, quote attribute values, image attributes, space and equal signs, avoid long code lines, blank lines, indentation, keep html, keep head, keep body, meta data, viewport, comments, stylesheets, loading JS into html, accessing HTML elements with JS, use lowercase file names, file extensions, index/default)

Learn CSS

Selections

Colors

Fonts

Positioning

Box model

Grid

Flexbox

Custom properties

Transitions

Animate

Make a simple modern static site

Learn responsive design

Viewport

Media queries

Fluid widths

rem units over px

Mobile first

Learn SASS

Variables

Nesting

Conditionals

Functions

Learn about CSS frameworks

Learn Bootstrap

Learn Tailwind CSS

Learn JS

Fundamentals

Document Object Model / DOM

JavaScript Object Notation / JSON

Fetch API

Modern JS (ES6+)

Learn Git

Learn Browser Dev Tools

Learn your VS Code extensions

Learn Emmet

Learn NPM

Learn Yarn

Learn Axios

Learn Webpack

Learn Parcel

Learn basic deployment

Domain registration (Namecheap)

Managed hosting (InMotion, Hostgator, Bluehost)

Static hosting (Nertlify, Github Pages)

SSL certificate

FTP

SFTP

SSH

CLI

Make a fancy front end website about 

Make a few Tumblr themes

===You are now a basic front end developer!

Learn about XML dialects

Learn XML

Learn about JS frameworks

Learn jQuery

Learn React

Contex API with Hooks

NEXT

Learn Vue.js

Vuex

NUXT

Learn Svelte

NUXT (Vue)

Learn Gatsby

Learn Gridsome

Learn Typescript

Make a epic front end website about 

===You are now a front-end wizard!

Learn Node.js

Express

Nest.js

Koa

Learn Python

Django

Flask

Learn GoLang

Revel

Learn PHP

Laravel

Slim

Symfony

Learn Ruby

Ruby on Rails

Sinatra

Learn SQL

PostgreSQL

MySQL

Learn ORM

Learn ODM

Learn NoSQL

MongoDB

RethinkDB

CouchDB

Learn a cloud database

Firebase, Azure Cloud DB, AWS

Learn a lightweight & cache variant

Redis

SQLlite

NeDB

Learn GraphQL

Learn about CMSes

Learn Wordpress

Learn Drupal

Learn Keystone

Learn Enduro

Learn Contentful

Learn Sanity

Learn Jekyll

Learn about DevOps

Learn NGINX

Learn Apache

Learn Linode

Learn Heroku

Learn Azure

Learn Docker

Learn testing

Learn load balancing

===You are now a good full stack developer

Learn about mobile development

Learn Dart

Learn Flutter

Learn React Native

Learn Nativescript

Learn Ionic

Learn progressive web apps

Learn Electron

Learn JAMstack

Learn serverless architecture

Learn API-first design

Learn data science

Learn machine learning

Learn deep learning

Learn speech recognition

Learn web assembly

===You are now a epic full stack developer

Make a web browser

Make a web server

===You are now a legendary full stack developer

[...]

(Computer system)=

Learn to execute and test your code in a command line interface

Learn to use breakpoints and debuggers

Learn Bash

Learn fish

Learn Zsh

Learn Vim

Learn nano

Learn Notepad++

Learn VS Code

Learn Brackets

Learn Atom

Learn Geany

Learn Neovim

Learn Python

Learn Java?

Learn R

Learn Swift?

Learn Go-lang?

Learn Common Lisp

Learn Clojure (& ClojureScript)

Learn Scheme

Learn C++

Learn C

Learn B

Learn Mesa

Learn Brainfuck

Learn Assembly

Learn Machine Code

Learn how to manage I/O

Make a keypad

Make a keyboard

Make a mouse

Make a light pen

Make a small LCD display

Make a small LED display

Make a teleprinter terminal

Make a medium raster CRT display

Make a small vector CRT display

Make larger LED displays

Make a few CRT displays

Learn how to manage computer memory

Make datasettes

Make a datasette deck

Make floppy disks

Make a floppy drive

Learn how to control data

Learn binary base

Learn hexadecimal base

Learn octal base

Learn registers

Learn timing information

Learn assembly common mnemonics

Learn arithmetic operations

Learn logic operations (AND, OR, XOR, NOT, NAND, NOR, NXOR, IMPLY)

Learn masking

Learn assembly language basics

Learn stack construct’s operations

Learn calling conventions

Learn to use Application Binary Interface or ABI

Learn to make your own ABIs

Learn to use memory maps

Learn to make memory maps

Make a clock

Make a front panel

Make a calculator

Learn about existing instruction sets (Intel, ARM, RISC-V, PIC, AVR, SPARC, MIPS, Intersil 6120, Z80...)

Design a instruction set

Compose a assembler

Compose a disassembler

Compose a emulator

Write a B-derivative programming language (somewhat similar to C)

Write a IPL-derivative programming language (somewhat similar to Lisp and Scheme)

Write a general markup language (like GML, SGML, HTML, XML...)

Write a Turing tarpit (like Brainfuck)

Write a scripting language (like Bash)

Write a database system (like VisiCalc or SQL)

Write a CLI shell (basic operating system like Unix or CP/M)

Write a single-user GUI operating system (like Xerox Star’s Pilot)

Write a multi-user GUI operating system (like Linux)

Write various software utilities for my various OSes

Write various games for my various OSes

Write various niche applications for my various OSes

Implement a awesome model in very large scale integration, like the Commodore CBM-II

Implement a epic model in integrated circuits, like the DEC PDP-15

Implement a modest model in transistor-transistor logic, similar to the DEC PDP-12

Implement a simple model in diode-transistor logic, like the original DEC PDP-8

Implement a simpler model in later vacuum tubes, like the IBM 700 series

Implement simplest model in early vacuum tubes, like the EDSAC

[...]

(Conlang)=

Choose sounds

Choose phonotactics

[...]

(Animation ‘movie’)=

[...]

(Exploration top-down ’racing game’)=

[...]

(Video dictionary)=

[...]

(Grand strategy game)=

[...]

(Telex system)=

[...]

(Pen&paper tabletop game)=

[...]

(Search engine)=

[...]

(Microlearning system)=

[...]

(Alternate planet)=

[...]

(END)

[alvdaz]

Star Citizen, le retour

Ah mes amis, la vie, quelle aventure !

Etant relativement disponible en ce moment *tousse*, je me suis dit que ça serait peut-être intéressant de refaire un tour sur Star Citizen. La dernière fois que j’en avais parlé ici, c’était il y a DEUX ans (en décembre 2017 pour être exact) et je me suis dit que ça serait pas mal de revenir dessus pour voir ce qui a changé, et démêler un peu le vrai du faux dans tout ce qui se dit sur ce jeu qui déchaîne les pa$$ions...

...

Ouais, ok, j’avoue, en vrai je veux pouvoir continuer à trasher ce jeu et le seul moyen de pouvoir lui allumer la gueule sans risquer de me faire crimetime par ses adeptes, c’est de connaître le sujet. C’est n’importe quoi, cette époque.

Bref, let’s go

Si vous avez lu mon précédent post à ce sujet, l’aspect Alpha du jeu transpirait par tous les pores. Nous sommes en 2019, le jeu est toujours en alpha MAIS des efforts ont été faits. 

Commençons par l’effort le plus notable: j’ai payé 60 balles. Oui, vous lisez bien, moi, Daz de Elite Dangerous du JDM, j’ai accepté de PAYER pour m’essayer à ce que je considère toujours comme étant une arnaque à grande échelle. Le calcul était simple: j’en avais assez de m’appeler Monsieur Lam et de conduire une Autobianchi spatiale (un Aurora). Donc dès que j’ai croisé un vaisseau starter qui me faisait un peu plus penser à ce que j’utilise dans Elite, j’ai dit banco. Désormais je suis donc DazJDM in-game et je pilote un Anvil C8X Pisces Expedition ou “Pisces” pour faire simple. C’est lui, là:

Il est tout choupi et il permet d’embarquer 3 personnes et du cargo, ce qui change des monoplaces sans aucune soute que j’utilisais jusqu’à présent. Pas de couchette en revanche, donc impossible de l’utiliser comme point de sauvegarde itinérant, je suis obligé d’aller me docker quelque part avant de déco (sinon on repart du dernier point de spawn et ça peut être un peu long).

Alors oui, vous m’insultez mais laissez-moi vous parler du 2nd effort observé: le jeu est désormais plutôt fluide. Tous les détails au taquet, en 2160x1440 (QHD), je tourne à 52 fps de moyenne. DE MOYENNE, CARL. Y a des drops quand on arrive sur des environnements complexes comme les planètes-villes mais rien d’insurmontable et surtout sans aucune comparaison avec les 17 fps ressentis en 2017, du côté de Port Olisar, l’historique station spatiale de départ. 

Mais si j’ai payé, c’est aussi parce que je considère que le jeu est arrivé à un point où il est tout à fait jouable.

Dans ce post, je ne parlerais que de ce qui existe et est actuellement visible in-game. Je n’aborderais pas les promesses de la CitizenCon comme le cycle météo, les mécaniques de survie et de gestion de la T° de notre avatar et toutes les sucreries évoquées le mois dernier par Chris Roberts. On reviendra dessus quand ça sera dispo (mdr).

En l’état le jeu est jouable donc et de mon point de vue ça passe par 2 aspects :

L’aire de jeu

La persistance (partielle, mais quand même)

Commençons par l’aire de jeu: Il y a 2 ans, nous n’avions en tout et pour tout que 3 lunes en orbite autour d’une géante gazeuse (Crusader) et la station de Port Olisar. 

Deux ans plus tard, à cette planète initiale se sont ajoutées 2 autres planètes (Hurston et ArcCorp) autour desquelles gravitent d’autres lunes et a priori l’update 3.8 prévu pour ce mois-ci devrait ajouter à la sauce une 4e planète nommée Microtech. Ajoutez à cela des ceintures d’astéroides, des stations intermédiaires et des outposts disséminés un peu partout à la surface des planètes. On a donc toujours qu’un seul système à se mettre sous la dent nommé Stanton, mais on peut réellement commencer à s’amuser. Je vous mets d’ailleurs une map du système en question pour que vous vous rendiez compte:

(Ok on voit que dalle, cliquez ICI pour ouvrir un carte lisible)

Là normalement les élitos qui me lisent vont me dire:

“Daz, t’as méfu, comment un seul système peut te satisfaire là où Elite t’en propose 400 milliards ?!?” 

Et ils n’auront pas tort. Ce qui sauve ce jeu, c’est sa gestion des distances. J’explique.

Dans Elite, le joueur a véritablement une stature de voyageur des étoiles. On peut se rendre n’importe où dans un système relativement vite et on peut sauter de système en système en un battement de cil, où que l’on se trouve. On sort d’une station et pouf, on se barre dans un système à 15 aL (années lumières) de là comme ça, littéralement à 3 km de la porte de la station.

Dans Star Citizen, c’est différent. Les sauts inter-systèmes ne peuvent se faire que via des Jump Points situés à des endroits précis et qui ne sont que des passages entre 2 systèmes uniques. Sur la capture du dessus, vous en voyez un qui permet(tra) d’aller dans le système Pyro localisé en haut à gauche. Cela veut dire que si un jour l’envie me prend d’aller à Pyro alors que je suis du côté de la planète Hurston, il va d’abord falloir que je couvre la distance Hurston-Jump Point avant. Et ce trajet intra-système mes amis, il ne se fait pas en 3 ou 4 minutes comme dans Elite. Il y a bien un mode de propulsion rapide baptisé Quantum Drive, mais ça n’a RIEN à voir avec le FrameShift Drive d’Elite. J’ai vérifié pendant un trajet, mon vaisseau couvre 1M de km en environ 22 secondes. Un trip entre Crusader (la gazeuse) et ArcCorp quand les 2 planètes sont diamétralement opposées avec l’étoile au milieu fait 50M de km. 50 x 22 = 1100 secondes soit 

DIX-HUIT MINUTES DE TRAJET

18 minutes en ligne droite pendant lesquelles tout peut arriver en plus. Et ensuite, il faut encore manoeuvrer, se docker et aller chercher l’objectif de la mission. 

Du coup, le jeu propose un truc qu’Elite peine à offrir au début: un sentiment d’appartenance à un endroit. D’être un peu “local” quoi. Dans Elite, on se limite généralement à visiter une station par système ou une planète au gré des missions et on checke notre statut et notre inventaire sagement docké en station. Dans Star Citizen le saut vers un autre système est déjà tellement un voyage en soi qu’un bicraveur peut parfaitement faire carrière en commerçant strictement intra-système. On utilise ces moments de trajet pour régler notre vaisseau, checker les missions, paramétrer notre stuff etc... C’est un parti-pris qui risque de mettre les explorateurs en galère, mais pour nous autres les traders, c’est ultra cool de connaître tous les points du système et de se dire qu’avant de livrer la came à tel endroit, va falloir faire un stop dans une station de refuel en chemin. Et je vous passe les bleds tentaculaires comme Lorville dans lequel on trouve un système de métro avec 4 lignes et des correspondances. Je peux vous dire que quand il a fallu que j’aille livrer une putain de caisse à la gate 02, au fin fond de la ligne rouge, je les ai senti passer les 15 minutes de trajet.

Deuxième point, la persistance. L’économie fonctionne à peu près et les thunes engrangées sont bien sauvegardées d’une partie à l’autre. Idem pour l’inventaire. Si vous quittez le jeu avec des caisses de marchandise dans votre vaisseau, vous le récupérerez avec les mêmes caisses situées au même endroit. Et ça c’est quand même cool et ça rend le jeu intéressant à jouer. Il y a toujours des wipes entre les différents patches mais -apparemment- la 3.8 permettra de conserver ses acquis, modulo les wipes souhaités par les devs. En attendant, si on se fait fait fumer, on ne perd pas ce qu’on était en train de faire. Je ne pense pas qu’il faille commencer à grinder comme des salauds pour autant puisque quoiqu’il arrive, tout ce qui a été obtenu en alpha sera dégagé en phase de béta puis de version release. Mais quand même, ça change du showroom virtuel qu’était le jeu il y a 2 ans. 

Illustration: je pars de Port Olisar pour aller sur une lune de Hurston. Trajet quantum, je chope la caisse en chemin et en arrivant sur la lune je foire ma descente, pour résumer, au dernier moment j’ai vu un autre joueur déjà posé à proximité de l’outpost donc j’ai voulu me poser + loin et m’approcher à pieds en fufu (les rencontres hors zones “d’armistice” sont généralement funestes) et en manœuvrant je m’explose comme une merde à une vingtaine de bornes de la destination. Pouf, je respawn sur Port Olisar mais Ô SURPRISE, la mission est toujours active et la caisse disponible. Je suis donc reparti sur cette lune située à 22M de km de là, me suis posé à proximité du cargo que  j’ai récupéré (je ne sais pas en quoi sont faites ces caisses mais boudiou c’est du solide) puis je suis allé à l’outpost et j’ai encaissé la prime. Et bah je peux vous dire que j’ai trouvé ça UUUUUULTRA COOL. C’était peut-être un bug remarquez parce qu’il parait que normalement les missions résistent pas à la mort (edit: non c’est normal en fait, les missions résistent à tout sauf à la déconnexion). Et les bugs, on va pas se mentir, c’est pas ce qui manque dans cette 3.7.

Du coup parlons-en de ce qui déconne dans Star Citizen

Le HUD est toujours nul à chier, l’affichage est parfois illisible avec, au pif, le soleil dans la gueule par exemple, ce qui n’arrive JAMAIS QUAND ON EST DANS L’ESPACE, LOL ! A côté de ça, tous les systèmes de vol sont aux fraises, on comprend rien, c’est inutilement compliqué, la gestion des limiteurs de vitesse et d’accélération est expliquée nulle part, y a 3 fonctions distinctes qui servent à peu près à la même chose bref c’est n’imp et faut vraiment prendre le temps de binder les fonctions sur le HOTAS pour tenter de comprendre à quoi ça sert, et en mode combat, c’est pire. La carte de navigation est dans le ton (à chier) avec une UI pas intuitive pour 2 sous et toujours uniquement appelable depuis le smartphone accroché au bras du perso et qu’on appelle avec F2. Ce qui veut dire que si je suis en vol et que je veux target une destination proche, faut que je quitte mon HOTAS pour repasser sur le clavier. C’est: NUL. Sinon, autre technique, je peux activer le Quantum Drive et tenter de m’y retrouver dans les 42 points de saut qui apparaissent partout à l’écran. Je peux vous dire que quand on veut se barrer d’une confrontation qui vire chocolat, c’est un véritable délice d’essayer de se battre avec l’affichage. 

Les missions sont toujours buguées parfois en bien (cf le cas précédent), souvent en mal (impossible de livrer le cargo à destination) et je ne parle que des missions basiques de delivery. J’ai pas encore testé les autres mais je ne me fais guère d’illusion. La fonction “attraper des trucs” m’a l’air d’être un bourbier sans nom qui semble être une surcouche ajoutée à la va-vite, à Port Olisar tout le monde se balade avec sa boite de fayots ou sa canette, c’est génialement useless. L’inventaire perso est gér�� comme le HUD et les systèmes de vol, c’est à dire que c’est trèèèèès moyen. Et c’est le problème de CIG avec cette volonté de mixer 3 modes de jeu en un seul. Faut faire le grand écart pour accorder tous les modes entre eux et on se retrouve avec résultat qui satisfait personne. Ajoutez à la sauce une centaine de vaisseaux et on comprend que la phase d’équilibrage risque de durer plus longtemps que le développement lui-même.

En gros, le jeu est très beau à regarder et parfois on tombe sur un truc encore en travaux, ça fait désordre, mais c’est une alpha. 

Alors, on prend ou pas ??

Franchement, y a déjà moyen de bien s’amuser en l’état. Si on se limite à l’existant, sans se préoccuper des promesses de Roberts ou du prix de vente débile des vaisseaux, on a un tout de même un titre assez solide et qui propose un terrain de jeu super vaste, très agréable à parcourir avec des potes. Ok, on a pas les 400 milliards de systèmes d’Elite, on en a même pas 2 à vrai dire, mais du coup le chiffre de 120 systèmes évoqués au début du dev me parait suffisant vu comment chaque système est déjà un univers en soi finalement. Si vous avez 60 balles à claquer, vous pouvez y aller mais uniquement si le contenu ACTUEL vous satisfait. J’insiste. Vous en aurez pour votre argent mais ne mettez pas plus et surtout, surtout, ne misez pas en écoutant les features miraculeuses de Chris Roberts qui dit que dans 9 mois ça sera génial ou celles de la communauté qui claque des mille et des cent en tentant de gratter la TVA au passage; les promesses n’engagent que ceux qui y croient et tout flatteur vit aux dépends de celui qui l’écoute. 

Cette leçon vaut bien un Pisces, sans doute. 

EDIT:

On m’a parlé sur Twitter des specs requises pour faire tourner le truc et c’est vrai que je l’ai pas précisé. Voici les specs de mon PC:

CPU: Ryzen 7 1700X (3,4 GHz)

RAM: 16 Go

GPU: 1080 Ti 

jeu installé sur un SSD

Avec ça, j’atteins donc les 52 fps de moyenne, à tout hasard, cette page permet de voir où se situe notre config par rapport à la config minimale et recommandée. 

[phulkor]

Docker cheat sheet

List docker images

docker image ls

List docker process

docker ps

Remove a docker image

(use docker image)

docker rmi -f <image-id>

Build a docker image

docker build -t <repo-url>:5000/<image-name> .

Push a docker image to a docker repo

docker push <image-name-with-repo>:latest

Pull a docker image

docker pull <image-name-with-repo>:latest

Run a docker image with port mapping

docker run -d -p 8081:7777 <image-name>

Show docker image logs

(use docker ps)

docker logs -f <container-id>

Attach to a terminal inside docker image

docker exec -it <container-id> /bin/sh

Remove all images matching a given name

docker rmi $(docker images |grep 'imagename')

[sztupy]

Irvine Welsh - The Sea @ Malmaison, 1 Tower Pl, Leith, Edinburgh, Scotland

The sea indirectly facilitated my transition from boy to man. More accurately, it stopped me from becoming the grown up I probably would have been. But strictly speaking my fate was decided not so much by the oceans themselves, but by another man from the port of Leith who had allowed the tides to define him. Like him, I was born very close to the water, but unlike him, I very rarely saw it. From our vantage, first from Leith tenement then Muirhouse flat, ‘the sea’ was visible only as the oily, dark, Firth of Forth, a river long gone tidal since its weaving adolescence in the Trossachs, as it bled slowly into the frozen North Sea.

The port and associated north Edinburgh schemes could occasionally be difficult terrain for a fledging (self described, they all are) intellectual. That horrendous archetype who wrote terrible poetry and wanted to seduce the kind of beautiful girl you saw on television, rather than (strictly) the ones next door. (This largely because you didn’t like the way she always wanted to hang out with her mum and big sister and looked at her latter’s children, and then to you, with challenging intent.) The girls on TV and in the movies, or the ones you saw up the toon at the festival, lived in different worlds, seemingly free from such oppressive ties. Those were the worlds I wanted access to. Meanwhile, the scheme ploughed on with its beautiful, raucous dramas that invigorated and frustrated in equal measure. Role models for masculinity were abundant and fascinating, but generally limited. That was my own fault: I always asked for and expected a hell of a lot more from life than most.

Of course, I wasn’t just an arty ponce. I loved football and boxing and music (I was only average at them all, which is worse than being bad, you simply stick around longer for more humiliation) and I could curse and drink with the best of my fellow spotty apprentices. I possessed a sharp and caustic tongue, which I sensed better fighters were often wary of. I tried on all the clothes; hard man, fanny merchant, joker, intellectual, politico, sharp dresser, drug addled waster, but none fitted correctly, and none would until I added the other special ingredient that made me more comfortable in my own skin. I had always craved the endless possibilities of travel. I wanted romance with somebody whose brother I didn’t know, someone who never baby sat for her younger siblings or her sister’s kids. I wanted to access lives I only had a vague idea ever existed. I was far from unhappy with my own life, in fact I loved it. I just wanted variety. I was curious.

It was one particular man of the sea who helped provide that pass. Let’s call him JL. He was a stick thin Samuel Beckett clone, a mate of my dad and uncle. A bunch of those ‘old boys’ as we called those men in their forties then, all from the docks, shipyards and maritime fleet, drank in the Marksman Bar in Duke Street. The old industrial working classes may have been on their way out, but back then they still ruled supreme. Unlike the dockers, who talked of thieving, and the tooled up shipyard workers at Robb Caledon, who talked violence, JL spun tales of the merchant seaman’s life, spiced with the intoxicating promise of sex and travel. It struck me fondly back then that young men need an uncle figure to tell them about carnal affairs. Your own dads are too embarrassed: "find a nice lassie, treat her right, and dinnae bring shame on this hoose" are admirable sentiments to live by, but also a little limiting. A road map to the good life they do not constitute on their own. Not for a poncy arty type.

JL had a different approach. His life was the sea, as it offered him freedom from not just confinement, but from attachment. He would move close in and advise us in his Grouse whisky breath, one eye shut, the other outrageously open, "get up the toon and fire intae they posh festival birds. Dinnae waste your time wi some wee hing oot fae The Spiral, you’ll never leave the scheme that wey." I sensed that JL was particularly directing those sentiments towards me. In my complete engagement, he read a fellow wandering soul. But like him, I didn’t so much want to leave the scheme as take it with me all around the world.  Out of the thirty or so of us who went to see our dads and the old boys for a pint before going our way on a pub crawl, which culminated in the Spiral or even some disco up the toon, only two of us, myself and three or four others, including the best looking guy in the mob, ventured as far as the Royal Mile and the pop up festival clubs. The other lads, (and they will probably kick fuck out of me for saying this), I think were a wee bit intimidated. It was out of their comfort zone.

JL however, was on hand to provide advice for every possible outcome of our romantic adventures. I recall one particular contention which was highly idiosyncratic and not empirically correct, but like all raconteurs, he knew that loose words spoken with conviction have a dynamism and charge that supersedes their content. ‘Wi posh birds you have to love them like thir cabin boys,’ he informed us. ‘Portuguese cabin boys are the best.’ When some of the other old guys heard this they would nervously bark: ‘Dinnae listen tae um. He’s talkin nonsense. He’s winding ye up.’

But I detected the strong waft of truth in his pithy disclosures.

We would later learn that JL had two families, one back in Granton and the other in Montevideo, or ‘Monty’ as he called the Uruguayan capital, in his unmistakable gravelly tones. And yes, it transpired that there was also a lover who was Portuguese, whom he’d worked with on several ships. This man came to Leith to find JL, probably to confront him about his treachery, perhaps bribe him or elicit some sort of commitment, (in the late seventies homosexual acts in Scotland were still illegal) but strangely, or perhaps not so, ended up lodging for several years with JL’s long suffering wife, EL. Of course, JL himself was gone. "Probably got another boat" his mates in the Marksman would mumble, resolutely set in non grass mode. But yes, it was inevitable that the old craggy couponed dog would be back at sea, or perhaps in ‘Monty’, with his second family. Or maybe there was a third set of kin somewhere, and I can see his progeny in Shanghai or Marseilles, briefly looking up from the mischief they were indulging in, perhaps wistfully gazing out to the sea. Wondering about its possibilities, and if they will ever allow it to make them.

It certainly helped to make me, for better and for worse, if only by the proxy of JL. I was on a train to London at sixteen and then a plane to New York at nineteen. I’ve never stopped moving since and it’s all down to JL and those strange lessons he gleaned from the sea.

About the creative team

Writer: Irvine Welsh was born in Edinburgh and is an acclaimed Scottish writer of novels, stories and stage and screenplays. He is most notably known for his novel, Trainspotting, written in 1993 that was eventually adapted into a film directed by Danny Boyle. More books have followed, Ecstasy and Filth being two that went straight to No 1 on the Sunday Times best-sellers list. He also branched into film and is a partner in two film production companies.

Visual Designer and Filmmaker: Norman Harman is an award-winning artist from Edinburgh. A graduate of Edinburgh College of Art, and winner of the RSA Latimer Prize for Painting, Harman's work has been exhibited internationally and he is a member of the art collective Ltd Ink Corporation. Harman’s practice incorporates painting, photography and moving image; exploring the discordant interference between analogue and digital processes. Deliberate digital misrepresentation reveals the beauty of lost transmissions and corrupted imagery. Harman's work allures to the space between abstraction and figuration through painting, digital and film.

Composer: Steve Mac is a music producer and DJ with over 25 years of experience in the music business. He began his career as a scratch mix DJ at the age of 11, but he is best known for being one half of the house music duo, Rhythm Masters. He often collaborates with Irvine Welsh on various music projects and have recorded 2 albums together. They are now taking the project live to the stage with many festival dates booked in for 2020.

About this location

Built in 1883, this building was originally a seaman’s mission which provided accommodation for sailors whose ships were in the Leith port, historically one of Scotland’s most important ports over the centuries. Over time, the building became known as a “house of ill repute,” but in 1994 it was bought and renovated by Malmaison, marking one of the first of many transitions to the Shore area of Leith. This was the first and remains the flagship hotel of this UK-based chain of boutique hotels.

[cornatul]

Using docker containers for development

Docker is a technology that allows users to bundle an application and run it within a loosely isolated environment referred to as a container. These containers are lightweight and self-contained, containing everything required to run the application without reliance on the host’s existing software. Containers can be shared effortlessly, ensuring that all recipients have access to the same working container.

Docker has become well-known for its deployment of production services such as application services and databases on enterprise servers or cloud instances. However, developers are increasingly employing containers for scenarios beyond deployment, including continuous integration, test automation, and complete software development environments, also known as development containers. These containers define a consistent environment in which an application can be developed before it is deployed.

One may question the benefits of containerizing the development environment. Have you ever found yourself cluttered with projects, libraries, languages, configurations, and tools when working on a new laptop or server? Wouldn’t it be beneficial to “restart” your software development environment to its original state?

Development containers provide a repeatable setup and consistent stateless development environment, allowing users to leave the underlying host free of project dependencies, specific language versions, and other factors. Furthermore, development containers enable users to utilize only the host machine’s computing resources. Finally, since the development environment is containerized, it can be replicated across many different systems with the Docker engine installed, ensuring a consistent development environment.

Numerous tools and services support the use of development containers, but Dockerfiles provide an option to customize your environment directly. Dockerfiles can extend images, add additional native OS packages, or make minor edits to the OS image. While many development images have been created by Microsoft available in Docker Hub, it is possible to create one from scratch.

To build a base development image, a parent image is required. The mcr.microsoft.com/vscode/devcontainers/universal image contains several runtime versions for popular languages, including Python, Node, PHP, Java, Go, C++, Ruby, and .NET Core/C#, as well as many popular tools and package managers. Using a custom Dockerfile, you can extend this image and add whatever you need.

For example, the Dockerfile shown above extends the parent image by first installing neovim and tmux to aid the development workflow. The user is then changed to codespace, and the working directory is set to the user’s home directory. Finally, configuration files for each tool are copied from the local machine.

Assuming the Dockerfile is in the same directory, the development image can be built with the following command:

$ docker build -t devcontainer .

The following command can be executed to start a development container from the newly created image:

$ docker run –privileged -it devcontainer bash

The -it flag opens an interactive container instance using bash as the Unix shell, and the –privileged flag starts the Docker container in privileged mode, granting the container root capabilities to all devices on the host system. This is beneficial when Docker is part of the development workflow. In addition, a volume can be mounted using the -v flag to persist data across different development containers, and a port can be mapped using the -p flag if developing a web application. This post was create by https://lzomedia.com

[thinkitiveblog]

Docker: How to get a Node.js application into a Docker Container

Introduction

The goal of this article is to show you an example of dockerizing a Node js application. Where you can have a basic understanding of Docker. It will help you to set up the Node js application and docker installation.

What is Docker?

Docker is an open-source platform for developing, shipping, and running applications. Docker enables you to separate your applications from your infrastructure so you can deliver software quickly. With Docker, you can manage your infrastructure in the same ways you manage your applications. By taking advantage of Docker’s methodologies for shipping, testing, and deploying code quickly, you can significantly reduce the delay between writing code and running it in production.

Why Docker?

Developing apps today requires so much more than writing code. Multiple languages, frameworks, architectures, and discontinuous interfaces between tools for each lifecycle stage create enormous complexity. Docker simplifies and accelerates your workflow while giving developers the freedom to innovate with their choice of tools. The day which comes in every developer’s life that application is working on our system, but It’s not working on the client’s system. To prevent this type of situation, we use Docker.

How can we use Docker with Nodejs?

Before starting, I am assuming that you have a working Docker installation and a basic understanding of how a Node.js application is structured.

In the first part of this video, we will create a simple web application in Node.js, then we will build a Docker image for that application, and lastly, we will instantiate a container from that image.

Setup Nodejs Server

Run command npm init and add the required details for your project

Install express in the project using npm I express

Then, create a server.js file that defines a web app using the Express.js framework:

Now we can test the node server, and start the application using node server.js. Let’s try to hit the URL http://localhost:8080/ and check the response

In the next steps, we’ll look at how you can run this app inside a Docker container using the official Docker image. First, you’ll need to create a docker file, Where we are going to add some commands.

#Dockerfile

Create a docker file in the root directory of the project using the touch command.

Edit the docker file using any editor and write the below instructions into the docker file.

Initially, we need to pick a node image that will run on a container, and here I am using the latest stable version of the node.

Next, we need to create a directory for the application. Here we can add all the project files.

This image comes with Node.js and NPM already installed, so the next thing we need to do is install your app dependencies using the npm install. So I am going to copy the package. JSON file.

To bundle your app’s source code inside the Docker image, use the COPY instruction:

Your app binds to port 8080 so you’ll use the EXPOSE instruction to have it mapped by the docker daemon:

Lastly, we are going to run the application using the CMD, which will execute node server.js

To see the final outputs please click here

[manavsmo-blog]

Top 6 Practices to Harden Docker Images to Enhance Security

Dockers can be considered equivalent to containers. Different verses of tools and platforms of containers are being used to develop containers to work more profitably. However, there are so many principles for protecting applications based on the container by collaborating with other secured applications.

We have described top 6 practices for Docker security into the most widespread Docker consulting that will be beneficial to build secure containers. If we see the infrastructure of traditional applications, we will find that the apps were hosted on bare or virtual machines.

On the other hand, containers are being used in Dockers that undermine the presumptions of clarity in the application. Due to this, many users face obstacles during the migration of Dockers and compare the usage of containers.

The user may have disorderly containers and servers, blind spots, or a much unprotected environment if you do not have an absolute arrangement and regular sustenance. If you’re also looking to work on Docker, you can take trusted docker consulting from 9series.

Through this article, we are going to discuss the most convenient practices for the security of Docker:

1. Confinement of network post convenience

Network ports are the most secure way to protect containers. The developers need to access the extra network ports to avoid hurdles at the development of the new container. After the image is entered into a composition or open internet atmosphere, it removes all the additional network ports.

While using Docker command-line interface (CLI), try to use the p parameters so that you can set limitations on host-to-container port mappings.

2. Apply Insignificant base images

The images in Docker are usually built on the top of “base images” to avoid the configuration of the image from scratching because it can cause a principal security issue. The component base images can also be used that are completely useless for your purposes.

Although, the additional component that you are using can expand the attack surface of your image. So it is necessary to select the base images carefully that can complement your target. If possible, you can also build a depreciated base image of your own.

3. Use of Docker Compose

This is the final way to harden your containers of Docker that you can combine all the files into Docker compose files. We can make them a public endpoint or public user access for the front end only when separating your network in the docker-compose method.

With this, your database will be limited only to container-to-container communication than the specific links. This method will increase the security of Dockers to the next level because there will be no public use that can connect to databases.

This method can be considered the most robust method of network segmentation for the architecture of the application. In this, all you need to divide the public-facing is the depletion of a flat network of containers.

There is no need to expose the database to the public internet. All they need is the minimal link of the narrow network so that you can communicate to the web series. As a result, when the database has been restricted, the chances of security issues decrease.

4. Secure the Host

The host is more protected than the Docker environment means if the host is compromised, then the containers are also at risk. So if you want to secure your containers, then first harden the host of containers, including an operating system, kernel versions, and system software. You can also do continuous patching and auditing for the hardening of the host.

5. Use Multi-Stage Builds

If you want your containers in an organized manner, then nothing can be better than a multi-stage build that provides operational and advantages of security. In this method, you can develop an intermediate container with all the necessary tools to generate the final artifact.

So lastly, only the final artifact will be copied in the final image without building temporary files or any developmental dependencies. Although it will only build the minimal binary files and the dependencies required for the final image without any intermediate files.

6. Use metadata labels for images

Labeling containers is the most basic practice that refers to the objects. The users can apply labels for additional information about the container. You can also characterize the containers by using tags, and this is what they are used for.

Conclusions

We hope that these fundamental points will help you to maintain a protected atmosphere for the container applications. As a result, The Center for Internet Security has put together a comprehensive benchmark for Docker with security guidelines for the Docker server software.

Now you can enjoy the advantages of Docker containers with the help of docker consulting from 9series without any obstacles in security only by using the outlined practices in the benchmark of CIS.

Source: 9series