To infinity and Beyond

To dump the contents of a file that contains the command-line arguments used to launch PostgreSQL, you can follow these steps:

Step 1: Locate the PostgreSQL Configuration File The first step is to locate the PostgreSQL configuration file. Depending on your operating system and PostgreSQL installation method, the configuration file can have different names and locations. Commonly, the configuration file is named postgresql.conf or postgres.conf.

On Linux, it is often located in the /etc/postgresql/<version>/main/ directory, where <version> is the PostgreSQL version you have installed. For example, /etc/postgresql/12/main/.

On Windows, it is typically found in C:\Program Files\PostgreSQL\<version>\data\.

Step 2: Open the Configuration File Once you have located the PostgreSQL configuration file, you can open it using a text editor like nano, vi, vim, gedit on Linux/Unix systems, or Notepad, Notepad++, or Visual Studio Code on Windows.

For example, on Linux, you can use the following command to open the configuration file using nano (you may need to use sudo if you don't have the necessary permissions):

Step 3: View the Contents After opening the file in your text editor, you should be able to see the contents, which typically include various configuration options for PostgreSQL, such as database paths, memory settings, authentication options, and more.

Step 4: Find the Command-Line Arguments Look for the section in the configuration file that specifies the command-line arguments used to launch PostgreSQL. This section is usually located at the beginning of the file or under the header Command-line options.

The command-line arguments might look something like this:

Step 5: Close and Save the File Once you have viewed the contents and found the relevant command-line arguments, save any changes you made to the file and close the text editor.

Remember that some PostgreSQL configurations may not be stored in the main postgresql.conf file. In such cases, you might have additional configuration files, such as pg_hba.conf for authentication settings or pg_ident.conf for user mapping. Be sure to check those files if you're looking for specific configuration details.

The configuration files will specify various settings and parameters, including server options and database connections, but they do not store the direct command-line arguments used at the time of launch.

brew services >> .plist >> value after -D is the data directory >> find postgres.config file to alter values

API: is way for two computers communicating each other

REST= Representational State Transfer

:Loose set of rules that has been the common standard building web API.

 An API that follows the REST standard called RESTful API

• Organise resources into a set of unique URIs(uniform resource identifier)
• The URIs differentiate different types of resources on a server
• HTTP verb which tells the server what we want to do with the resource
• POST(create), GET(read), PUT(Update), DELETE(remove)
• body is where payload of data is stored usually encoded in JSON
• stateless: no need to store any info about each other, every req & res is independent from all others.>> easy to scale and well-behaved. 
• versioning: allow breaking changes from one version to another>> providing backward compatibility

The resources should be grouped by noun

The client interact with a resource by making a res to the end point for the resource over HTTP. The req has a very specific format.

Req status

200 level (success)

400 level (something wrong with our request)

500 level (something wrong at the server level)

Idemponent: making multiple identical requests has the same effect as making a single request (not case for POST)

Cacheable/Performance

What makes service RESTful?

A RESTful service is a type of web service that follows the principles of Representational State Transfer (REST). Here are some of the characteristics that make a service RESTful:

1. Client-server architecture: The client and server are separate and independent components that communicate through a stateless protocol.
2. Statelessness: Each request from the client to the server contains all the necessary information to complete the request. The server doesn't store any client state between requests.
3. Uniform interface: The interface between the client and server is standardized, which means that the client and server can be developed independently.
4. Resource-based: RESTful services are resource-based, meaning that the server represents the state of the resource to the client.
5. Cacheability: Responses from the server can be cached on the client or intermediaries.
6. Layered architecture: Intermediaries can be used to improve scalability, performance, and security.

By following these principles, a service can be considered RESTful, which can provide benefits such as simplicity, scalability, and flexibility.

Why RESTful? Benefits?

Response Code?

You have an end point of a brute force attack (1000 of attempts of attack)>> how to mitigate the attack

If req is sent from Postman/command promt/web, how can you insure the req is from web not from Postman..?

What would be your matric to say if this is good or bad code

Junior/Intermediate/Seniour responsibilites

PM wants to get some feature to be done, what matrix that transforms your business logic to working coordination.

[01]

​

창업부트캠프

본 과정 리뷰하기

전체적으로 좋은 강의였다.

돌다리 이론 부터 그에 따른 마케팅이 어떻게 들어가야 하는 지 또한 김성공님은 어떻게 해결하셨는지 알 수있어서 좋았던거 같다.

사실 꽤나 반복적인 이야기들이 있어서 집중도가 선행학습때에 비교해서 꽤나 떨어 진거 같다. 복습의 중요함이 있지만서도 선행학습에 비해서 집중도가 많이 떨어졌던게 사실이다. 

마케팅 강의에서도 페북 같이 광고 돌리는 법이 조금 아쉬웠다. 실제로 어떻게 하셨는지 보여 주셨다면 이해하기 쉽고 바로 적응할 수 있지 않을까라는 생각이든다. 

카피라이팅은 정말 알찼던거 같다. 매우 디테일하고 확고한 전략으로 실행에 바로 옮길 수 있지 않았나 싶다.

네이버 카페 같이 로직을 알려주는 것도 정말 유용했다. 아마 강의 내용이 약간 유튜브 강의 느낌으로 즉석에서 하는 느낌이 나지 않았나 싶다. 약간에 몰입도가 방해된것 같다.

아이엠웹페이지는 전반적인 내용을 보여주기에 적합한 강의지 않았나 싶다.

전체적으로 강의와 강사님의 스타일이 다르기 때문에 학교에서 과목마다 가르치는 선생님이 다른 느낌이었다. 

하지만 뭣보다 중요한건 실행력이고 복습인 것 같다. 

나의 문제도 너무나도 완벽하게 계속 생각해내려는 것 같다.

오늘 부터 한번 쭉 바로 페북 광고를 태워보는 걸로 시작해봐야 겠다.

망고 보드를 써봤는데.. 뭔가 엉성하네요.. 어렵기도 하고..

더 많이 만들어 봐야 겠네요..

[01]

​

잠재 고객의 블로그, 캠프원 블로그 방문하여 이웃 5명 이상 늘리고 인증하는 글쓰기

내가 알아야 할 블로그, 같은 데이터 베이스를 축적할 수 있을만한 블로그를 모았다.

비슷한 모임을 축적해서 사람을 모으는 노하우가 생길것 같다.